CVE-2026-39918: Vvveb < 1.0.8.1 Code Injection via Installation Endpoint
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Vvvebto a version that resolves this vulnerability.Fixed in 1.0.8.1 - Compensating control
Protect the Vvveb installation endpoint (where the subdir POST parameter is written to env.php) by restricting access to trusted IPs/authenticated users (e.g., via web server/WAF/ACL) to prevent unauthenticated exploitation.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39918?
CVE-2026-39918 is rated as a high severity vulnerability due to the potential for code injection.
How do I fix CVE-2026-39918?
To fix CVE-2026-39918, upgrade Vvveb to version 1.0.8.1 or later where the vulnerability has been patched.
What type of vulnerability is CVE-2026-39918?
CVE-2026-39918 is a code injection vulnerability affecting the installation endpoint of Vvveb.
What impact can CVE-2026-39918 have on my application?
Exploitation of CVE-2026-39918 can allow attackers to execute arbitrary code on the server through the env.php configuration file.
Which versions of Vvveb are affected by CVE-2026-39918?
Vvveb versions prior to 1.0.8.1 are vulnerable to CVE-2026-39918.