# CVE-2026-92915: WWBN AVideo userVerifyEmail.php Unauthenticated Access Control

> Unauthenticated attackers can enumerate users and trigger password recovery tokens, potentially leading to account takeover via verification email links.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-rg4h-fcmm-8w26, GHSA-wphj-4v3g-8q6c

## What is CVE-2026-92915?

CVE-2026-92915 is a medium-severity missing authorization vulnerability in WWBN AVideo, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-92915?


## How do I fix CVE-2026-92915?

No fix has been published for CVE-2026-92915 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92915 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92915 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92915 and fix it if it is affected.

What it is: CVE-2026-92915 is a medium-severity missing authorization vulnerability in WWBN AVideo, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92915 exists.

Affected product: WWBN AVideo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92915/ (Markdown: https://insights.sbomify.com/CVE-2026-92915/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92915
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92915
- OSV: https://osv.dev/vulnerability/CVE-2026-92915

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92915/
Summaries are generated and may contain mistakes; the official description above is the record.