# CVE-2026-41929: Vvveb < 1.0.8.2 Unauthenticated Reflected XSS via Visual Editor

> Unauthenticated attackers can execute arbitrary JavaScript via reflected XSS in the visual editor, potentially leading to account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/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:** 7 May 2026
- **Updated:** 28 Jul 2026

## What is CVE-2026-41929?

CVE-2026-41929 is a medium-severity cross-site scripting vulnerability in givanz Vvveb, published on 7 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.2 contains an unauthenticated reflected cross-site scripting vulnerability in the visual editor preview renderer that allows attackers to execute arbitrary JavaScript by manipulating the r query parameter and _component_ajax POST parameter. Attackers can craft a malicious link or auto-submitted form that causes victims to execute attacker-controlled JavaScript in the context of the Vvveb origin, as the gating function isEditor() performs no session, role, or token verification and the view handler injects raw HTML POST body content without sanitization.

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

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


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

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

## Is CVE-2026-41929 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41929 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41929 is a medium-severity cross-site scripting vulnerability in givanz Vvveb, published on 7 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41929 exists.

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-41929/ (Markdown: https://insights.sbomify.com/CVE-2026-41929/index.md)
```

## Sources

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

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