CVE-2026-41932

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-05-14. the CNA's CVSS baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

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

Vvveb before 1.0.8.3 contains a stored cross-site scripting vulnerability in the customer signup flow where the Signup::addUser() controller copies raw POST username values into the display_name field before sanitization occurs. Attackers can submit HTML and script markup in the username field during signup, which gets stripped from the username column but persisted verbatim in the display_name column, allowing stored XSS execution when display_name is rendered without encoding in vulnerable views.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

May 14, 2026

Last Modified

July 28, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
Patch available. Sources: github_commit, github_release.
generic

Vvveb < 1.0.8.3 Stored XSS via Signup Controller | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vvveb-stored-xss-via-signup-controller
github_release Patch Available

Vvveb 1.0.8.3

Patch available: givanz/Vvveb 1.0.8.3

https://github.com/givanz/Vvveb/releases/tag/1.0.8.3
github_commit Patch Available

commit fefac290a8c8 (givanz/Vvveb)

Patch available: givanz/Vvveb 1.0.8.3 (contains commit fefac290a8c8)

https://github.com/givanz/Vvveb/commit/fefac290a8c85d3c87fe80ffed68b6c5bc50e93c

Weakness Classification(1)

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

Frequently asked(5)

What is CVE-2026-41932?
CVE-2026-41932 is a medium vulnerability published on May 14, 2026. Vvveb before 1.0.8.3 contains a stored cross-site scripting vulnerability in the customer signup flow where the Signup::addUser() controller copies raw POST username values into the displayname field before sanitization occurs. Attackers can submit HTML and script markup in the username field…
When was CVE-2026-41932 disclosed?
CVE-2026-41932 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41932 actively exploited?
CVE-2026-41932 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 87.7% of all scored CVEs.
What is the CVSS score of CVE-2026-41932?
CVE-2026-41932 has a CVSS v4.0 base score of 6.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41932?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41932, 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-41932

Explore →

Is Your Infrastructure Affected by CVE-2026-41932?

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