CVE-2026-61564

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-112507 (ENISA EUVD)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

AVideo is a video-sharing Platform. Prior to 8.1.0, the unauthenticated installer endpoint install/checkConfiguration.php assembles videos/configuration.php by interpolating request parameters, including webSiteRootURL, into single-quoted PHP string literals without escaping. An attacker can terminate a literal and inject PHP that executes as the web-server user when the generated, directly requestable file is loaded. Exploitation requires videos/configuration.php to be absent, as on every fresh deployment or after the file is removed or moved; an existing file blocks this endpoint. The supplied systemRootPath must contain index.php and a connection using databaseHost, databaseUser, and databasePass must succeed, but the attacker can point those parameters to their own database server and needs no target credentials. The write location is also derived from systemRootPath without a base-directory constraint. This permits arbitrary command execution, reading and overwriting files owned by the web-server user, persistent PHP code, and control over stored database connection settings. The endpoint additionally interpolates request values into streamer and configuration INSERT statements, creating a secondary SQL-injection sink. This issue is fixed in version 8.1.0.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

November 3, 2026

Advisory Details (3)

Auto-updated Nov 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unauthenticated Arbitrary PHP File Write Leading to Remote Code Execution via the Installer Endpoint in AVideo-Encoder · Advisory · WWBN/AVideo-Encoder · GitHub

https://github.com/WWBN/AVideo-Encoder/security/advisories/GHSA-xrj3-cqm8-r992
GitHub release Patch Available

v8.1.0

Patch available: WWBN/AVideo-Encoder v8.1.0

https://github.com/WWBN/AVideo-Encoder/releases/tag/v8.1.0
GitHub commit Patch Available

commit 0faaddebd11c (WWBN/AVideo-Encoder)

Patch available: WWBN/AVideo-Encoder v8.1.0 (contains commit 0faaddebd11c)

https://github.com/WWBN/AVideo-Encoder/commit/0faaddebd11c087885d25a7e0513745465cad411

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 18:19 UTCEchelonGraph re-scored
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-11-11 20:23 UTCEchelonGraph re-scored
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-10 22:26 UTCEchelonGraph re-scored
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-11-10 00:10 UTCEchelonGraph re-scored
  8. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-11-09 02:13 UTCEchelonGraph re-scored
  10. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-11-08 04:18 UTCEchelonGraph re-scored
  12. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-11-07 06:15 UTCEchelonGraph re-scored
  14. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  15. 2026-11-06 14:25 UTCOSV refresh
  16. 2026-11-06 08:19 UTCEchelonGraph re-scored
  17. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  18. 2026-11-05 10:23 UTCEchelonGraph re-scored
  19. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  20. 2026-11-04 12:26 UTCEchelonGraph re-scored
  21. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  22. 2026-11-03 14:29 UTCEchelonGraph re-scored
  23. 2026-11-03 13:55 UTCEchelonGraph re-scored
  24. 2026-11-03 05:34 UTCEchelonGraph re-scored
  25. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
Show 12 more
  1. 2026-11-02 07:36 UTCEchelonGraph re-scored
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-11-01 09:40 UTCEchelonGraph re-scored
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-31 11:45 UTCEchelonGraph re-scored
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-10-30 13:48 UTCEchelonGraph re-scored
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-10-28 22:26 UTCEchelonGraph re-scored
  10. 2026-10-28 22:01 UTCENISA EUVD ID recordedEUVD-2026-112507 · Source: ENISA EUVD
  11. 2026-10-28 21:48 UTCEchelonGraph re-scoredFirst assessed: 10.0 CRITICAL
  12. 2026-10-28 21:48 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61564?
CVE-2026-61564 is a critical-severity vulnerability; its CVE record was published on October 28, 2026. AVideo is a video-sharing Platform. Prior to 8.1.0, the unauthenticated installer endpoint install/checkConfiguration.php assembles videos/configuration.php by interpolating request parameters, including webSiteRootURL, into single-quoted PHP string literals without escaping. An attacker can…
When was the CVE record for CVE-2026-61564 published?
The CVE record for CVE-2026-61564 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-61564 actively exploited?
CVE-2026-61564 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61564?
CVE-2026-61564 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61564?
A fix for CVE-2026-61564 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61564?

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

Book a Demo →Browse All CVEs