Wp VrWordPress extension · Rextheme
CVE-2023-40663
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Rextheme WP VR plugin <= 8.3.4 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in Rextheme WP VR WordPress plugin versions 8.3.4 and below allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in the server response without proper output encoding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp VrWordPress extension
<= 8.3.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the WP VR plugin installationAccess your WordPress installation via file system or FTP. The plugin is typically located in /wp-content/plugins/wp-vr/ or check via WordPress admin dashboard under Plugins.Affected if The plugin directory wp-vr/ exists in the plugins folder
-
Identify the installed versionCheck the main plugin file (usually wp-vr/index.php or wp-vr/wp-vr.php) for the version comment header, or look in the plugin's readme.txt file under the '== Changelog ==' section for the version number.Affected if The version number found is 8.3.4 or lower (e.g., 8.3.4, 8.3.3, 8.3.0, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm WP VR shows as 'Active', or check the wp_options table for the active_plugins option.Affected if The plugin is enabled and running on the WordPress site
-
Check for the vulnerable reflected parameterExamine HTTP responses from plugin endpoints by submitting a test request with a harmless string like 'test123' in the URL query parameters used by the plugin (common paths include /wp-admin/admin-ajax.php?action=wpvr_ or similar frontend endpoints). Inspect if this input is reflected verbatim in the response without HTML encoding.Affected if User-supplied input is reflected in the response without proper encoding (e.g., <script> tags render as literal text rather than being escaped)
Your environment is affected if the WP VR plugin version 8.3.4 or lower is installed and active on your WordPress site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the WP VR plugin to a version newer than 8.3.4, or implement WAF rules to filter XSS payloads until the patch can be applied.
Fix this in Wp Vr
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-40663 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data