CVE-2026-114429 WPVR CVE debrief

Who should care

Defenders responsible for WordPress installations with the WPVR plugin should assess exposure and prioritize updating to version 9.0.3 or later. This includes reviewing Contributor role access controls and monitoring for suspicious activity on the affected tour. Defenders should also verify the WPVR plugin version and review compensating controls for exposed systems.

Why it matters

Defenders should prioritize verifying and updating the WPVR WordPress plugin to prevent potential Stored Cross-Site Scripting attacks.

• Potential for Stored Cross-Site Scripting attacks
• Possible execution of malicious code in the browser of users viewing the affected tour
• Verification of WPVR plugin version and Contributor role access controls required

Technical summary

The WPVR WordPress plugin before 9.0.3 does not properly sanitise and escape some of its tour hotspot content before storing it and outputting it on the front end, which could allow users with the Contributor role and above to perform Stored Cross-Site Scripting attacks. This vulnerability allows for potential Stored Cross-Site Scripting attacks, impacting users viewing the affected tour. Defenders should assess exposure and prioritize updating to version 9.0.3 or later, and restrict Contributor role and above access to sensitive content.

Defensive priority

Defenders should prioritize verifying and updating the WPVR WordPress plugin to version 9.0.3 or later, and restrict Contributor role and above access to sensitive content.

Recommended defensive actions

• Verify and update the WPVR WordPress plugin to version 9.0.3 or later
• Restrict Contributor role and above access to sensitive content
• Monitor for suspicious activity on the affected tour
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability, with the primary source being the WPSCAN reference. The WPSCAN reference provides details on the vulnerability, including the affected plugin version and potential impact. Defenders should verify the WPVR plugin version and review Contributor role access controls.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.