CVE-2026-54506

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th 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-82571 (ENISA EUVD)Source: ENISA EUVD

7.6EG
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.4%CVSS: 7.6Exploit: 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, app/controller/user/profile.php accepts the user[bio] field and passes stored content through sanitizeHTML() in system/functions.php, whose on* event-handler regular expression omits the forward-slash delimiter and whose do-while condition compares the string to itself, so forbidden nested tags are removed only once. An Author-role or higher user can submit solidus-prefixed event-handler markup or nested forbidden tags that survive sanitization. The stored bio is rendered without sufficient output encoding on /author/{username}, in the admin user-management view, and potentially in comment displays, causing attacker-controlled JavaScript to execute when unauthenticated visitors, administrators, or other users view the content. This can expose browser-session data and permit victim-context account actions, defacement, or phishing. This issue is fixed in version 1.0.8.5.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 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.4%
EPSS %ILE
28th
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 (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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 23, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
Patch available. Sources: github_commit, github_release, github.
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 20a01ef08559 (givanz/Vvveb)

Patch available: givanz/Vvveb 1.0.8.5 (contains commit 20a01ef08559)

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

Stored XSS via sanitizeHTML() bypass in user profile bio field · Advisory · givanz/Vvveb · GitHub

https://github.com/givanz/Vvveb/security/advisories/GHSA-5cg7-phhv-4qjr

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 46× 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-02 16:45 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-31 11:22 UTCEG score recompute
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-25 14:19 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-24 07:50 UTCEG score recompute
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-18 03:30 UTCEG score recompute
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-17 04:14 UTCEG score recompute
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 54 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-12 15:56 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:48 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-11 05:52 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-09 21:01 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-08 22:59 UTCEG score recompute
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-08 00:33 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-06 15:42 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-06 04:20 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-05 06:27 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-03 21:36 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-10-02 23:38 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  26. 2026-10-02 01:43 UTCEG score recompute
  27. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-09-30 16:52 UTCEG score recompute
  29. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-09-29 18:41 UTCEG score recompute
  31. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-29 07:42 UTCEG score recompute
  33. 2026-09-28 20:46 UTCEG score recompute
  34. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-09-27 22:54 UTCEG score recompute
  36. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-09-27 01:01 UTCEG score recompute
  38. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  39. 2026-09-26 03:09 UTCEG score recompute
  40. 2026-09-24 18:17 UTCEG score recompute
  41. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-09-23 20:24 UTCEG score recompute
  43. 2026-09-23 19:20 UTCEG score recompute
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-09-22 23:02 UTCEG score recompute
  46. 2026-09-22 01:10 UTCEG score recompute
  47. 2026-09-21 03:18 UTCEG score recompute
  48. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-09-19 18:30 UTCEG score recompute
  50. 2026-09-18 20:37 UTCEG score recompute
  51. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-09-17 22:23 UTCEG score recompute
  53. 2026-09-17 21:54 UTCEG score recomputeFirst assessed: 7.6 HIGH
  54. 2026-09-17 21:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54506?
CVE-2026-54506 is a high-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, app/controller/user/profile.php accepts the user[bio] field and passes stored content through sanitizeHTML() in system/functions.php, whose on* event-handler regular expression…
When was the CVE record for CVE-2026-54506 published?
The CVE record for CVE-2026-54506 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-54506 actively exploited?
CVE-2026-54506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54506?
CVE-2026-54506 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54506?
A fix for CVE-2026-54506 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-54506

Explore →

Is Your Infrastructure Affected by CVE-2026-54506?

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

Book a Demo →Browse All CVEs