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

> Attackers can inject malicious scripts via the signup username field, leading to stored XSS execution when the display name is rendered.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-prv3-g5c7-jrxh

## What is CVE-2026-41932?

CVE-2026-41932 is a medium-severity cross-site scripting vulnerability in givanz Vvveb, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-41932?


## How do I fix CVE-2026-41932?

No fix has been published for CVE-2026-41932 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41932 being exploited?

There is no known exploitation of CVE-2026-41932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41932 and fix it if it is affected.

What it is: CVE-2026-41932 is a medium-severity cross-site scripting vulnerability in givanz Vvveb, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41932 in the wild and no public exploit code.

Affected product: givanz Vvveb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41932/ (Markdown: https://insights.sbomify.com/CVE-2026-41932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41932
- OSV: https://osv.dev/vulnerability/CVE-2026-41932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41932/
Summaries are generated and may contain mistakes; the official description above is the record.