CVE-2026-41932: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in givanz Vvveb
Vvveb versions before 1.0.8.3 have a stored cross-site scripting (XSS) vulnerability in the customer signup flow. The vulnerability arises because the Signup::addUser() controller copies raw POST username values into the display_name field without proper sanitization. While the username column strips HTML and script markup, the display_name column persists this data verbatim. This allows stored XSS execution when the display_name is rendered without encoding in certain views. The CVSS 4.0 base score is 5.3, indicating a medium severity vulnerability.
AI Analysis
Technical Summary
CVE-2026-41932 is a stored cross-site scripting vulnerability in givanz Vvveb prior to version 1.0.8.3. The issue occurs in the customer signup flow where the Signup::addUser() controller copies raw POST username input into the display_name field before sanitization. Although the username column removes HTML/script markup, the display_name field retains it verbatim. When display_name is rendered without proper encoding in vulnerable views, this enables stored XSS attacks. The vulnerability has a CVSS 4.0 score of 5.3 (medium severity). No patch or official remediation level has been published, and no exploits are known in the wild.
Potential Impact
An attacker can submit malicious HTML or script code in the username field during signup, which is stored unsanitized in the display_name field. This stored malicious content can execute in the context of users viewing affected pages, potentially leading to session hijacking, defacement, or other XSS-related impacts. The vulnerability requires user interaction (UI:P) and has low complexity (AC:L). It does not require privileges or authentication (PR:N) and has limited impact on confidentiality and integrity but some impact on availability and security controls as per the CVSS vector.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing input sanitization and output encoding on the display_name field to prevent script execution. Avoid rendering display_name without proper encoding in any views. Monitor vendor communications for updates on patches or official mitigations.
CVE-2026-41932: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in givanz Vvveb
Description
Vvveb versions before 1.0.8.3 have a stored cross-site scripting (XSS) vulnerability in the customer signup flow. The vulnerability arises because the Signup::addUser() controller copies raw POST username values into the display_name field without proper sanitization. While the username column strips HTML and script markup, the display_name column persists this data verbatim. This allows stored XSS execution when the display_name is rendered without encoding in certain views. The CVSS 4.0 base score is 5.3, indicating a medium severity vulnerability.
CVSS v4.0
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41932 is a stored cross-site scripting vulnerability in givanz Vvveb prior to version 1.0.8.3. The issue occurs in the customer signup flow where the Signup::addUser() controller copies raw POST username input into the display_name field before sanitization. Although the username column removes HTML/script markup, the display_name field retains it verbatim. When display_name is rendered without proper encoding in vulnerable views, this enables stored XSS attacks. The vulnerability has a CVSS 4.0 score of 5.3 (medium severity). No patch or official remediation level has been published, and no exploits are known in the wild.
Potential Impact
An attacker can submit malicious HTML or script code in the username field during signup, which is stored unsanitized in the display_name field. This stored malicious content can execute in the context of users viewing affected pages, potentially leading to session hijacking, defacement, or other XSS-related impacts. The vulnerability requires user interaction (UI:P) and has low complexity (AC:L). It does not require privileges or authentication (PR:N) and has limited impact on confidentiality and integrity but some impact on availability and security controls as per the CVSS vector.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing input sanitization and output encoding on the display_name field to prevent script execution. Avoid rendering display_name without proper encoding in any views. Monitor vendor communications for updates on patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-04-22T18:50:43.620Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a05e885ec166c07b0eee23e
Added to database: 05/14/2026, 15:21:41 UTC
Last enriched: 05/21/2026, 15:46:54 UTC
Last updated: 07/02/2026, 08:51:19 UTC
Views: 62
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.