# CVE-2026-41934: Vvveb < 1.0.8.2 Authenticated RCE via Code Editor

> Authenticated users can achieve remote code execution by uploading malicious files via the admin code editor due to insufficient extension restrictions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-vfjj-gcvv-w248

## What is CVE-2026-41934?

CVE-2026-41934 is a high-severity code injection vulnerability in givanz Vvveb, published on 6 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vvveb before version 1.0.8.2 contains an authenticated remote code execution vulnerability in the admin code editor that allows low-privilege authenticated users to execute arbitrary code through insufficient file extension restrictions, with the uploaded payload then executable via subsequent unauthenticated HTTP requests. Attackers with editor, author, contributor, or site_admin roles can write a malicious .htaccess file to map arbitrary extensions to the PHP handler, then upload PHP code with that extension to achieve unauthenticated remote code execution when the file is accessed via HTTP.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

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


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

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

## Is CVE-2026-41934 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41934 is a high-severity code injection vulnerability in givanz Vvveb, published on 6 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41934 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-41934/ (Markdown: https://insights.sbomify.com/CVE-2026-41934/index.md)
```

## Sources

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

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