# CVE-2026-39918: Vvveb < 1.0.8.1 Code Injection via Installation Endpoint

> Unauthenticated attackers can achieve remote code execution by injecting PHP code into the installation endpoint's configuration file.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-chhv-69jq-q952

## What is CVE-2026-39918?

CVE-2026-39918 is a critical code injection vulnerability in givanz Vvveb, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vvveb prior to 1.0.8.1 contains a code injection vulnerability in the installation endpoint where the subdir POST parameter is written unsanitized into the env.php configuration file without escaping or validation. Attackers can inject arbitrary PHP code by breaking out of the string context in the define statement to achieve unauthenticated remote code execution as the web server user.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-39918 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39918 is a critical code injection vulnerability in givanz Vvveb, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39918 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-39918/ (Markdown: https://insights.sbomify.com/CVE-2026-39918/index.md)
```

## Sources

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

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