Quick answers
- Is CVE-2026-55231 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55231 being exploited in the wild.
- How severe is CVE-2026-55231?
- High severity, with a CVSS score of 7.2, published 1 October 2026.
- Which products and versions are affected?
- Vvveb before 1.0.8.6.
- Is there a fix for CVE-2026-55231?
- Yes: fixed in 1.0.8.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55231 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-55231?
- 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.
How to fix
- Fixed in: 1.0.8.6
Technical details
The sanitizeFileName() function in system/functions.php uses a single-pass regex that fails to prevent path traversal when special characters are interspersed with dots (e.g., ".!." becomes ".." after filtering). Authenticated users with the default site_admin role can reach backup controllers that call sanitizeFileName() without secondary realpath() validation, allowing arbitrary file read via the download() action and arbitrary file delete via the delete() action. The vulnerability requires authentication and backup role membership but affects sensitive endpoints with no additional containment checks.
Affected products
- Vvveb Vvveb before 1.0.8.6
Timeline
- 2026-06-11: advisory
- 2026-06-11: patched: version 1.0.8.6 released