Quick answers
- Is CVE-2026-114429 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114429 being exploited in the wild.
- How severe is CVE-2026-114429?
- Informational severity, published 24 October 2026.
- Which products and versions are affected?
- WPVR before 9.0.3.
- Is there a fix for CVE-2026-114429?
- Yes: fixed in 9.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114429 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114429?
- Check whether you run WPVR 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: 9.0.3
Technical details
The plugin fails to properly sanitize and escape tour hotspot content before storage and output, allowing authenticated users with Contributor role or above to perform stored XSS attacks (CWE-79). An attacker with appropriate WordPress permissions can inject arbitrary JavaScript that persists and executes for all users viewing the affected tour, without requiring user interaction or additional authentication.
Affected products
- WPVR WPVR before 9.0.3
Timeline
- 2026-10-22: disclosed
- 2026-10-24: advisory