# CVE-2026-92913: AVideo Weak PRNG Activation Code Authentication Bypass

> Weak PRNG in AVideo allows unauthenticated attackers to guess activation codes and obtain long-lived credentials, leading to account takeover.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/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-cv5x-3jv8-pgmr, GHSA-v65f-hc7x-wj62

## What is CVE-2026-92913?

CVE-2026-92913 is a critical 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

AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 uses a cryptographically weak pseudo-random number generator when creating account activation / login pairing codes. getRandomCode() in objects/functions.php derives the code entirely from uniqid() (sprintf('%08x%05x', seconds, microseconds)) with a single non-CSPRNG rand() character used only as padding, reducing the code space to roughly 36 x 10^6 (~2^25) values for a known generation second. Because plugin/API/set.json.php?APIName=login_code can be called without authentication, it also serves as an oracle for the server's exact microtime. An unauthenticated remote attacker who guesses a valid, unexpired code (codes expire after 10 minutes) can redeem it at plugin/API/get.json.php?APIName=login_code to obtain the target account's email address and a User::getUserHash(users_id, '+1 year') value, a credential accepted in place of the account password for one year, resulting in account takeover. No patched version is available.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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


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

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

## Is CVE-2026-92913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92913 is a critical 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-92913 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-92913/ (Markdown: https://insights.sbomify.com/CVE-2026-92913/index.md)
```

## Sources

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

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