CVE-2026-54506

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: None knownExposed: 0

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

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.6(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity76% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
🔬 Proof of concept available. 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 Patch Available🟡 PoC Available

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 5× in last 7d / 5× 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-18 20:37 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 22:23 UTCEG score recompute
  4. 2026-09-17 21:54 UTCEG score recompute
  5. 2026-09-17 21:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54506?
CVE-2026-54506 is a high vulnerability 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 CVE-2026-54506 disclosed?
CVE-2026-54506 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-54506 actively exploited?
CVE-2026-54506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54506?
CVE-2026-54506 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-54506?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54506, 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-54506

Explore →

Is Your Infrastructure Affected by CVE-2026-54506?

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