Quick answers
- Is CVE-2026-41929 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41929 being exploited in the wild.
- How severe is CVE-2026-41929?
- Medium severity, with a CVSS score of 6.1, published 7 May 2026.
- Which products and versions are affected?
- Givanz Vvveb CMS before 1.0.8.2.
- Is there a fix for CVE-2026-41929?
- A patch was published on 2026-05-04: Fix committed and version 1.0.8.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41929 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41929?
- Check whether you run Givanz Vvveb CMS 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
A reflected cross-site scripting (XSS) vulnerability exists in Vvveb CMS due to insufficient authentication and input sanitization in the visual editor's preview functionality. The 'isEditor()' function in 'system/functions.php' incorrectly validates editor status based solely on the presence of the 'r' query parameter without verifying sessions or roles. Consequently, the view handler in 'system/core/view.php' accepts raw HTML from the 'html' POST parameter and injects it directly into the response body when '_component_ajax' is present. An unauthenticated attacker can exploit this by crafting a malicious link or auto-submitting form to execute arbitrary JavaScript in a victim's browser. This vulnerability was patched in version 1.0.8.2 by adding proper admin and user key checks.
Affected products
- givanz Vvveb CMS before 1.0.8.2
Timeline
- 2026-04-27: other: Vulnerability validated
- 2026-05-04: patched: Fix committed and version 1.0.8.2 released
- 2026-05-04: advisory: GitHub Security Advisory published
- 2026-05-07: disclosed: CVE published to NVD