Quick answers
- Is CVE-2026-55230 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55230 being exploited in the wild.
- How severe is CVE-2026-55230?
- High severity, with a CVSS score of 8.7, published 1 October 2026.
- Which products and versions are affected?
- Vvveb <= 1.0.8.5.
- Is there a fix for CVE-2026-55230?
- 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-55230 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-55230?
- 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 sanitizeHTML() function in system/functions.php uses a regex pattern anchored on the first greater-than character (>) to strip event handlers, allowing an attacker to bypass the filter by placing a greater-than character inside a quoted attribute value (e.g., src="x>"). This causes the regex to terminate early and leave the event handler intact, resulting in stored XSS executed in visitor and administrator browsers within the origin context. An authenticated low-privilege author can submit the payload through the page editor; the JavaScript executes client-side with access to session cookies and CSRF tokens.
Affected products
- Vvveb Vvveb <= 1.0.8.5
Timeline
- 2026-06-11: disclosed
- 2026-06-11: patched