# CVE-2026-41936: Vvveb < 1.0.8.2 XML External Entity Injection via Import

> Authenticated site admins can exploit XXE in the import feature to read arbitrary files and escalate privileges by overwriting password hashes.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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-rfxr-4xpm-wrp7

## What is CVE-2026-41936?

CVE-2026-41936 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 XML external entity (XXE) injection vulnerability in the admin Tools/Import feature that allows authenticated site_admin users to read arbitrary files and modify database records. Attackers can exploit the XML parser configuration in system/import/xml.php to inject file:// or php://filter entity references that are resolved and persisted into the application database, enabling arbitrary file disclosure and administrator password hash overwriting for privilege escalation.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2026-41936 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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