OCTOBER 13, 2026
Live Feed
Back to database
Case File

CVE-2026-92915

HIGH · CVSS 7.3 EPSS 0.42% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-17 · Last synced 2026-10-13

CyberRota Analysis

AI-Generated

The vulnerability in WWBN AVideo allows unauthenticated remote attackers to exploit broken access controls in the user verification process, enabling them to send an unlimited number of verification emails to any user account and enumerate account verification statuses. This flaw also permits attackers to generate and embed password recovery tokens in the verification links, potentially compromising user accounts. Organizations using this software should prioritize addressing this vulnerability, as it poses a significant risk to user account security and integrity.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-92915
Severity
HIGH
CVSS
7.3
EPSS
0.42%

Original NVD Description

WWBN AVideo through commit e01e41ecc (no patched version available) contains a broken access control flaw in objects/userVerifyEmail.php. The script disables the login requirement ($global['ignoreUserMustBeLoggedIn'] = 1), takes users_id directly from the query string, and calls User::sendVerificationLink() with no session requirement, no CSRF/global token, no relationship check between caller and target, and no enforceRateLimit() call. The only intended throttle is keyed to the caller's own session, so cookie-less requests are never limited. An unauthenticated remote attacker can therefore cause an arbitrary number of verification emails to be sent to any account ID, and can enumerate accounts and their verification status from the three distinct JSON responses ("Verification Sent", "Already verified", "Unknown error"). In addition, createVerificationCode() invokes $user->setRecoverPass() and saves the user, so each anonymous request writes a live password-recovery token onto the targeted account; that token is embedded in base64 in the verification link emailed to the account owner and is accepted by objects/userRecoverPassSave.json.php as the credential for setting a new password.