Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-exploitable token replay requiring no authenticated session (PR:N) but AC:H because capturing a valid in-flight token is a necessary precondition; no availability impact applies.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
Vulnerability-Lookup contains an authentication weakness in its account activation and password-recovery mechanism. Activation and recovery links were generated using stateless signed tokens containing only the user's login. Although the token signature and age were validated, the application did not track whether a token had already been successfully used. As a result, a captured activation or password-recovery link remained valid for the entire configured TOKEN_VALIDITY_PERIOD, even after the associated password had been changed.
An attacker who obtains a valid activation or recovery token could therefore replay it multiple times during its validity period to set a new password and repeatedly take control of the affected account. In addition, tokens were not bound to a specific purpose, allowing the same token mechanism to be used across activation and recovery workflows. The patch introduces purpose-bound tokens and a random nonce whose SHA-256 digest is stored with the user account. The nonce is invalidated after a successful password change, making tokens single-use, while issuing a new token invalidates any previously issued token. The password-setting operation now explicitly consumes the token before committing the account change.
Successful exploitation requires the attacker to obtain a currently valid activation or recovery link, but does not require knowledge of the victim's existing password or an authenticated session.
AnalysisAI
Token replay in Vulnerability-Lookup's account activation and password-recovery mechanism allows an attacker who captures a valid one-time link to repeatedly reset the victim's password throughout the entire TOKEN_VALIDITY_PERIOD, even after the legitimate user has already consumed that token. Because the application never records whether a token has been used and does not bind tokens to a specific workflow, a single intercepted link grants persistent account-takeover capability without requiring any knowledge of the victim's current credentials. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the attacker to possess a currently valid, unexpired account activation or password-recovery token URL for the target account - specifically a link generated by Vulnerability-Lookup's activation or recovery workflow and still within the configured TOKEN_VALIDITY_PERIOD. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The provided CVSS 4.0 score of 8.8 (AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N) reflects network-exploitable account takeover with high impact on both the vulnerable system and subsequent systems - the latter plausible given Vulnerability-Lookup's role as a threat intelligence platform where account compromise could expose or manipulate sensitive CVE data downstream. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker targets a Vulnerability-Lookup user who recently requested a password reset and intercepts the recovery email - via a compromised mail server, a shared inbox, or by tricking the user into forwarding the link. The attacker submits the token URL to set a new password and gain full account access, then replays the same link repeatedly during the TOKEN_VALIDITY_PERIOD to regain control even after the legitimate user attempts to recover their account using the same link. … |
| Remediation | The primary fix is to update Vulnerability-Lookup to the version incorporating commit bef837242657acf680832be56b94428df130ed67, available at https://github.com/vulnerability-lookup/vulnerability-lookup/commit/bef837242657acf680832be56b94428df130ed67; no independently confirmed patched release version number is available at time of analysis. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify the current Vulnerability-Lookup version and confirm patch availability from the vendor, then prepare deployment procedures with your infrastructure team. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Vulnerability Lookup
View allSSRF guard bypass in Vulnerability Lookup's webhook notification subsystem allows a network attacker to register a webho
Stored cross-site scripting in Vulnerability-Lookup's render_tag_badges Jinja filter allows an authenticated user holdin
Inconsistent authorization enforcement in Vulnerability-Lookup's SSE streaming interface allows self-registered but unco
Server-side request forgery in Vulnerability-Lookup's remote-instance synchronization feature enables an authenticated a
Same weakness CWE-294 – Authentication Bypass by Capture-replay
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-57226
GHSA-w4vj-gm7w-293h