CVE-2026-92913

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(high)
EG Risk
49(Track*)
EG Risk 49/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

AVideo Weak PRNG Activation Code Authentication Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/avideo-weak-prng-activation-code-authentication-bypass
github Patch Available🟡 PoC Available

Use of a cryptographically weak PRNG: `getRandomCode()` activation codes are a pure function of server microtime, and redeeming one returns a one-year authentication token · Advisory · WWBN/AVideo · GitHub

https://github.com/WWBN/AVideo/security/advisories/GHSA-v65f-hc7x-wj62

Vendor Advisories for CVE-2026-92913(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 09:08 UTCGHSA enrichment
  2. 2026-09-18 22:00 UTCEG score recompute
  3. 2026-09-18 22:00 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 10:52 UTCGHSA enrichment
  6. 2026-09-17 23:44 UTCEG score recompute
  7. 2026-09-17 23:44 UTCGHSA enrichment
  8. 2026-09-17 12:20 UTCEG score recompute
  9. 2026-09-17 12:10 UTCEG score recompute
  10. 2026-09-17 11:29 UTCEG score recompute
  11. 2026-09-17 11:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92913?
CVE-2026-92913 is a high vulnerability published on September 17, 2026. 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,…
When was CVE-2026-92913 disclosed?
CVE-2026-92913 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92913 actively exploited?
CVE-2026-92913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.5% of all scored CVEs.
What is the CVSS score of CVE-2026-92913?
CVE-2026-92913 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-92913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92913, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92913

Explore →

Is Your Infrastructure Affected by CVE-2026-92913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs