Quick answers
- Is CVE-2026-54612 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54612 being exploited in the wild.
- How severe is CVE-2026-54612?
- High severity, with a CVSS score of 8.8, published 17 September 2026.
- Which products and versions are affected?
- Vvveb 1.0.0 through 1.0.8.4.
- Is there a fix for CVE-2026-54612?
- A patch was published on 2026-06-07: Version 1.0.8.5 released with sanitization fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54612 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-54612?
- Check whether you run Vvveb at an affected version. 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
The vulnerability exists in saveGlobalElements() within admin/controller/editor/global-trait.php, which concatenates user-controlled file paths from the data-v-save-global parameter directly to the theme directory without proper sanitization before passing to loadHTMLFile() and file_put_contents(). An authenticated user with the default Editor role and editor/* permission can submit crafted HTML to module=editor/editor&action=save to traverse outside the theme directory and overwrite existing writable PHP files. If web-accessible, the attacker can leverage the shipped public/vadmin/index.php entrypoint to execute editor-controlled PHP code. The fix in version 1.0.8.5 adds path sanitization and removes the editor/* permission for the Editor role.
Affected products
- Vvveb Vvveb 1.0.0 through 1.0.8.4
Timeline
- 2026-09-17: disclosed
- 2026-06-07: patched: Version 1.0.8.5 released with sanitization fix