dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-47452

CRITICAL · 9.9 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Unrestricted Upload of File with Dangerous Type vulnerability in RexTheme WP VR wpvr allows Upload a Web Shell to a Web Server.This issue affects WP VR: from n/a through <= 8.5.26.

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 · high confidence

Unrestricted file upload vulnerability in the WP VR WordPress plugin allows authenticated attackers to upload malicious files (web shells) to the server, potentially achieving remote code execution. The vulnerability stems from insufficient validation of uploaded file types in the plugin's upload functionality.

MitigationUpdate WP VR plugin to version 8.5.27 or later. If immediate update is not possible, disable the file upload functionality or restrict upload permissions to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP VR plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-vr' or 'wp-vr-boomerang' or similar RexTheme VR plugin folders. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to list all plugins.
    Affected if The WP VR plugin folder exists in the plugins directory or appears in the WordPress admin plugin list.
  2. Determine installed version of WP VR
    Open the main plugin file (usually wp-content/plugins/[vr-plugin-folder]/wp-vr.php or similar) and look for the 'Version' header in the plugin comments. Alternatively, check wp-content/plugins/[vr-plugin-folder]/readme.txt for the 'Stable tag' entry.
    Affected if The version number is 8.5.26 or lower, or if no version is found but the plugin is present (assume vulnerable).
  3. Check for suspicious PHP files in upload directories
    Scan the wp-content/uploads/ directory (and subdirectories) for .php files, especially those with generic names like shell.php, upload.php, cmd.php, or recently modified PHP files. Use: find wp-content/uploads/ -name '*.php' -type f 2>/dev/null
    Affected if Any PHP files are found in the uploads directory, as WordPress should not serve PHP from uploads by default.
  4. Review access to file upload functionality
    Check if the plugin's upload endpoint is accessible. Test by submitting a request to the suspected upload URL (common paths include /wp-json/wp/vr/upload or /wp-admin/admin-ajax.php?action=vr_upload). Check the plugin's PHP code for upload handling functions that lack capability checks or nonce validation.
    Affected if The upload functionality accepts files without authentication requirements or proper validation, indicated by missing current_user_can() checks or wp_verify_nonce() calls in the upload handler code.

A user is affected if the WP VR plugin is installed with version 8.5.26 or lower, or if unknown PHP files are found in the uploads directory indicating possible exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP VR plugin to version 8.5.27 or later. If immediate update is not possible, disable the file upload functionality or restrict upload permissions to trusted users only.

Recommended fix Moderate confidence

Upgrade to a version higher than 8.5.26 (latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WP VR (RexTheme WP VR) plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository or RexTheme website
  6. 6. After updating, verify the plugin is functioning correctly
  7. 7. Test that file upload functionality works as expected for legitimate VR content

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47452 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47452 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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