Quick answers
- Is CVE-2026-39918 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39918 being exploited in the wild.
- How severe is CVE-2026-39918?
- Critical severity, with a CVSS score of 9.8, published 20 April 2026.
- Which products and versions are affected?
- givanz Vvveb < 1.0.8.1.
- Is there a fix for CVE-2026-39918?
- A patch was published on 2026-04-19: Version 1.0.8.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39918 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-39918?
- Check whether you run Givanz VvvebJs. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A code injection vulnerability exists in Vvveb versions prior to 1.0.8.1 within the installation endpoint. The root cause is the lack of sanitization, escaping, or validation of the 'subdir' POST parameter before it is written to the 'env.php' configuration file. An unauthenticated remote attacker can provide a specially crafted 'subdir' value to break out of the PHP string context in a 'define' statement. This allows the injection of arbitrary PHP code, leading to remote code execution (RCE) with the privileges of the web server user. The issue is addressed in version 1.0.8.1 by implementing proper filename sanitization.
Affected products
- givanz Vvveb < 1.0.8.1
Timeline
- 2026-04-19: patched: Version 1.0.8.1 released
- 2026-04-20: advisory: CVE published and VulnCheck advisory released