dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-6222

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-18
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 No privileges 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
The WooCommerce Refund And Exchange with RMA - Warranty Management, Refund Policy, Manage User Wallet theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'ced_rnx_order_exchange_attach_files' function in all versions up to, and including, 3.2.6. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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

The WooCommerce Refund And Exchange plugin versions up to 3.2.6 contains an arbitrary file upload vulnerability in the 'ced_rnx_order_exchange_attach_files' function. The function lacks file type validation, allowing unauthenticated attackers to upload any file type to the server. This can lead to remote code execution if executable files (e.g., PHP scripts) are uploaded and accessed.

MitigationUpdate the plugin to version 3.2.7 or later which contains the vendor patch. If an update is unavailable, implement file type validation with an allowlist, disable PHP execution in upload directories, and consider disabling the affected function until a patch is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Confirm plugin installation
    Check if 'WooCommerce Refund And Exchange with RMA' plugin is installed in your WordPress environment. Look for the plugin directory at wp-content/plugins/woo-refund-and-exchange-with-rma/ or check via WordPress admin plugins page.
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed plugin version
    Locate the main plugin file (usually index.php or the primary plugin file) and check the version declared in the plugin header comment, or query the WordPress database wp_options table for the option containing the plugin version.
    Affected if The installed version is lower than 3.2.7 (the version with the fix)
  3. Verify vulnerable function exists
    Inspect the plugin files, searching for the function 'ced_rnx_order_exchange_attach_files' to confirm it exists in the installed version. This function handles file uploads in the exchange request feature.
    Affected if The function 'ced_rnx_order_exchange_attach_files' is present in the plugin code
  4. Check if WooCommerce is active
    Verify that WooCommerce is installed and active, as this plugin is a WooCommerce extension and the vulnerable feature handles exchange request attachments.
    Affected if WooCommerce is active and the plugin is enabled
  5. Test endpoint accessibility
    Identify the AJAX or form endpoint that calls 'ced_rnx_order_exchange_attach_files' - typically reachable at wp-admin/admin-ajax.php or a frontend AJAX handler. Attempt a safe test request (without uploading) to confirm the endpoint responds and is accessible to unauthenticated users if the WordPress site allows unauthenticated exchange requests.
    Affected if The file upload endpoint is accessible without authentication

You are affected if the plugin is installed with a version before 3.2.7 and the vulnerable file upload function is present and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.2.7 or later which contains the vendor patch. If an update is unavailable, implement file type validation with an allowlist, disable PHP execution in upload directories, and consider disabling the affected function until a patch is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6222 — 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-6222 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