Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-84480 – Password Recovery Token Expiration Bypass Leading to Account Takeover – WWBN AVideo

Be the first to know when new zero-days emerge:

Summary

CVE-2026-84480 is a critical insufficient session/token expiration vulnerability (CWE-613) in WWBN AVideo’s password recovery workflow. The endpoint that finalizes a password reset, userRecoverPassSave.json.php, fails to enforce the recovery token’s expiration window, allowing an attacker holding a previously issued token to reset a victim’s password at any time. The flaw carries a CVSS score of 9.3 and can lead to full account takeover, including administrator accounts.

Technical details

  • Root cause: userRecoverPassSave.json.php performs a raw string comparison of the recovery token instead of calling isRecoverPassValid()/checkRecoverPass(), which enforces the intended 24-hour token validity window.
  • A separate ownership-check bug uses a less-than (<) comparison instead of strict equality (===), allowing a token issued for a higher user ID to also validate against lower user IDs, including the administrator account.
  • Attack vector: Network, no authentication or user interaction required; the attacker only needs to obtain a recovery token that was previously generated (e.g., from old emails, backups, logs, or archives).
  • Impact: Because tokens never truly expire and ownership checks can be bypassed, an attacker can reset arbitrary account passwords indefinitely, resulting in complete account compromise and, for admin accounts, full control of the AVideo installation.

Affected software

  • WWBN AVideo, all versions from 0 through 29.0
  • Confirmed vulnerable up to commit e01e41ecc and earlier

Severity

  • CVSS v4.0: 9.3 (Critical) — AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H
  • CVSS v3.1: 9.8 (Critical) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No official patched release is currently available. The project maintainers have published a suggested source-code fix (suggested-fix.patch) that replaces the direct token comparison with checkRecoverPass() and corrects the ownership check to use strict equality; apply this patch to userRecoverPassSave.json.php as an interim fix.
  • If unable to patch: Restrict or disable the password recovery feature from the internet-facing interface, rotate all admin and user passwords, invalidate/expire all existing recovery tokens at the database level, and monitor logs for repeated or delayed use of userRecoverPassSave.json.php requests.
  • Track the vendor repository for an official release that resolves GHSA-j9p7-hm85-9v77 and upgrade as soon as it is published.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Sign In - AVideo, AVideo
  • Raw response body: id="avideoModal", avideoAlert(, avideoModalIframe(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge