Unauthenticated code execution via installer subdir injection
Published Apr 20, 2026 · Updated Apr 20, 2026
Code injection in Vvveb before 1.0.8.1 allows remote attackers to execute PHP code through the web-based installation endpoint. The install() method in install/controller/index.php inserts the untrusted subdir value into an env.php define string without escaping or validation. Exploitation requires the installation workflow to be reachable and runs injected code with the web server user's privileges.
Summary
What happened
Code injection in Vvveb before 1.0.8.1 allows remote attackers to execute PHP code through the web-based installation endpoint. The install() method in install/controller/index.php inserts the untrusted subdir value into an env.php define string without escaping or validation. Exploitation requires the installation workflow to be reachable and runs injected code with the web server user's privileges.
The record
- CVE
- CVE-2026-39918
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- givanz
- Product
- Vvveb
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo