LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41932: Vvveb < 1.0.8.3 Stored XSS via Signup Controller

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.

MediumCVSS 6.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Vvveb versions before 1.0.8.3 can store malicious markup submitted through customer signup. Although the username is cleaned, the related display name may retain the original input. If a vulnerable page later displays that value without encoding, an attacker’s script could run in another user’s browser, potentially exposing data or changing actions within that session.

Executive priority

Prioritize remediation for public-facing installations with open signup, especially where customer names appear in administrative or authenticated views. The issue is moderate rather than critical because user interaction is required and availability is unaffected, but unauthenticated input can become persistent browser-executed content. Upgrade during the next expedited maintenance window and investigate stored data.

Technical view

Signup::addUser() copies the raw POST username into display_name before username sanitization. Malicious markup is therefore removed from username but may remain stored in display_name and execute in views lacking output encoding. The issue is remotely reachable without authentication but requires a victim to view affected content. It is classified as CWE-79 with CVSS 3.1 score 6.1.

Likely exposure

Internet-facing Vvveb installations running versions before 1.0.8.3 are the likely exposure, particularly where public customer signup is enabled and display_name appears in unencoded views. The source bundle does not identify every vulnerable view or configuration, so deployment-specific validation is required.

Exploitation context

The CVSS vector indicates network access, low complexity, no privileges, and required user interaction. Stored execution may cross security boundaries and cause limited confidentiality or integrity impact. The supplied sources do not report active exploitation, and the CVE is not listed as KEV in the bundle.

Researcher notes

The vulnerable data flow is raw POST username to display_name before sanitization, creating inconsistent treatment between username and display_name. Successful impact depends on a downstream view rendering display_name without encoding. The bundle names release 1.0.8.3 and commit fefac290a8c85d3c87fe80ffed68b6c5bc50e93c as remediation references but does not enumerate all affected sinks.

Mitigation direction

  • Upgrade Vvveb to version 1.0.8.3 or later using the vendor release guidance.
  • Confirm the referenced security patch is present if maintaining a customized Vvveb build.
  • Temporarily restrict public signup where upgrading cannot be completed promptly.
  • Review stored display names for unsafe markup and remediate them using a controlled process.
  • Ensure every display_name rendering context applies appropriate output encoding.

Validation and detection

  • Inventory Vvveb deployments and identify their exact versions or source commit.
  • Verify production systems include release 1.0.8.3 or the referenced patch commit.
  • Confirm signup processing cannot persist raw markup into display_name.
  • Review templates and views that render display_name for context-appropriate encoding.
  • Safely inspect existing display_name records for unexpected HTML or script markup.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41932 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7VulnCheck
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2026-41932Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
givanzVvveb0, fefac290a8c85d3c87fe80ffed68b6c5bc50e93caffected
Weakness

CWE details

CWE-79

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs