WWBN AVideo fails to validate password recovery token expiration in userRecoverPassSave.json.php, allowing attackers to use expired tokens to reset account passwords indefinitely. Attackers who obtain a recovery token can use it at any time to change the target account's password and gain full account access.
Security readout for executives and security teams
Plain-English summary
AVideo may accept expired password-recovery tokens indefinitely. Anyone who obtains an old token could reset its account’s password and take control without further user interaction. Compromised privileged accounts could expose content, user data, and service administration.
Executive priority
Treat as an urgent identity-control issue. Promptly determine whether AVideo is deployed and externally reachable, then follow vendor remediation guidance. Prioritize installations containing sensitive data or privileged administrative accounts.
Technical view
The flaw is missing expiration validation in userRecoverPassSave.json.php. It is classified as CWE-613 and scored CVSS 3.1 9.8 because exploitation is remote, low complexity, and may fully affect confidentiality, integrity, and availability. An attacker must first possess a recovery token.
Likely exposure
Deployments using AVideo’s affected password-recovery flow may be exposed, particularly when publicly reachable. The supplied affected-version data lists version “0” while declaring other versions unaffected, so the precise vulnerable release range cannot be established from this bundle.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. Exploitation nevertheless requires no authenticated account or user interaction after an attacker obtains a recovery token. How tokens might be acquired is not documented here.
Researcher notes
The vulnerable handler is identified as userRecoverPassSave.json.php, with expiration enforcement absent from the recovery-token save path. CWE-613 fits insufficient session expiration. The supplied version metadata is ambiguous, so researchers should avoid asserting a broader affected range without vendor confirmation.
Mitigation direction
Check the vendor advisory immediately for confirmed affected and fixed versions.
Apply the vendor-supported fixed release when identified.
Invalidate existing recovery tokens where supported, especially for privileged accounts.
Temporarily restrict password-recovery access if exposure cannot be promptly resolved.
Monitor password resets and subsequent account activity for anomalies.
Validation and detection
Inventory all AVideo deployments and record their exact versions.
Compare deployed versions with the vendor advisory’s confirmed affected range.
Verify through authorized testing that expired recovery tokens are rejected.
Review logs for unexpected password resets and unfamiliar post-reset access.
Confirm privileged accounts have no outstanding recovery tokens where observable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-613: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-613 · source CWE mapping
Insufficient Session Expiration
Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.