CVE-2026-54613

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th 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-82569 (ENISA EUVD)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.3%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.5, getThemeFolder() in admin/controller/editor/revisions.php returns the attacker-controlled theme parameter without sanitization, and backupFolder() concatenates it beneath DIR_THEMES before editor/revisions/load or editor/revisions/delete operates on a named .html file. sanitizeBackupFileName() strips traversal characters only from the separate file parameter and does not protect the theme directory component. An authenticated user with the default Editor role and editor/* permission can submit traversal sequences that redirect file_get_contents() or unlink() to a reachable backup subdirectory outside the web root. A valid admin session and CSRF token are required, the read is limited to .html files in backup directories, and deletion additionally requires filesystem write permission. This can disclose sensitive exported site content or remove backup data. This issue is fixed in version 1.0.8.5.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.3%
EPSS %ILE
27th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

September 17, 2026

Last Modified

September 22, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

Vvveb 1.0.8.5

Patch available: givanz/Vvveb 1.0.8.5

https://github.com/givanz/Vvveb/releases/tag/1.0.8.5
GitHub commit Patch Available

commit 1d76ad52402b (givanz/Vvveb)

Patch available: givanz/Vvveb 1.0.8.5 (contains commit 1d76ad52402b)

https://github.com/givanz/Vvveb/commit/1d76ad52402beeed623a7e386c6796126689a746
GitHub advisoryMentions a patch (unverified)

Path Traversal in Revision Backup Reader/Deleter via Unsanitized theme Parameter · Advisory · givanz/Vvveb · GitHub

https://github.com/givanz/Vvveb/security/advisories/GHSA-gjxp-vrcw-69v8

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-10-30 11:25 UTCOSV refresh
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-10-25 14:19 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-10-22 21:20 UTCEG score recompute
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-18 03:30 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 49 more
  1. 2026-10-12 15:56 UTCEG score recompute
  2. 2026-10-11 19:39 UTCEG score recompute
  3. 2026-10-11 16:54 UTCEG score recompute
  4. 2026-10-11 14:17 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-11 11:38 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-10 13:37 UTCEG score recompute
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-10-08 17:34 UTCEG score recompute
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-06 19:46 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-05 21:45 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-04 23:45 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-10-04 01:44 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-03 03:44 UTCEG score recompute
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-02 05:40 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-01 07:34 UTCEG score recompute
  26. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  27. 2026-09-30 09:34 UTCEG score recompute
  28. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  29. 2026-09-29 11:24 UTCEG score recompute
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  31. 2026-09-27 15:20 UTCEG score recompute
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-26 17:19 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-24 20:31 UTCEG score recompute
  36. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-09-23 22:31 UTCEG score recompute
  38. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-23 00:30 UTCEG score recompute
  40. 2026-09-22 02:29 UTCEG score recompute
  41. 2026-09-22 02:01 UTCEG score recompute
  42. 2026-09-21 14:47 UTCEG score recompute
  43. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-09-19 18:38 UTCEG score recompute
  45. 2026-09-18 20:37 UTCEG score recompute
  46. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-09-17 22:24 UTCEG score recompute
  48. 2026-09-17 21:54 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  49. 2026-09-17 21:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54613?
CVE-2026-54613 is a medium-severity vulnerability; its CVE record was published on September 17, 2026. Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.5, getThemeFolder() in admin/controller/editor/revisions.php returns the attacker-controlled theme parameter without sanitization, and backupFolder() concatenates it beneath…
When was the CVE record for CVE-2026-54613 published?
The CVE record for CVE-2026-54613 was published on September 17, 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 September 22, 2026; the record at its source may have been updated since.
Is CVE-2026-54613 actively exploited?
CVE-2026-54613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54613?
CVE-2026-54613 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54613?
A fix for CVE-2026-54613 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-54613

Explore →

Is Your Infrastructure Affected by CVE-2026-54613?

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

Book a Demo →Browse All CVEs