# CVE-2026-41938: Vvveb < 1.0.8.2 RCE via Media Upload Handler

> Authenticated attackers can upload malicious files to achieve remote code execution on Vvveb CMS installations.

- **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

## What is CVE-2026-41938?

CVE-2026-41938 is a high-severity 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 unrestricted file upload vulnerability in the media upload handler that allows authenticated users with media-upload permissions to bypass extension restrictions by uploading a .htaccess file to map .phtml extensions to the PHP handler. Attackers can upload a .phtml file containing arbitrary PHP code and execute the uploaded payload through a subsequent unauthenticated HTTP GET request to the uploaded file, resulting in remote code execution with web server privileges.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-41938 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41938 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41938 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-41938/ (Markdown: https://insights.sbomify.com/CVE-2026-41938/index.md)
```

## Sources

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

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