dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-12881

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
The Return Refund and Exchange For WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.5.5 via the wps_rma_fetch_order_msgs() due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read other user's order messages.

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 Return Refund and Exchange For WooCommerce plugin contains an Insecure Direct Object Reference (IDOR) vulnerability in the wps_rma_fetch_order_msgs() function in versions up to 4.5.5. The function fails to validate that the requesting user has proper authorization to access the requested order messages, allowing any authenticated user with Subscriber-level access or higher to read order messages belonging to other users by manipulating a user-controlled key parameter.

MitigationUpdate the plugin to version 4.5.6 or later which includes proper authorization validation. Until updated, consider restricting subscriber-level account creation or implementing additional access controls at the web application firewall level.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Verify the plugin is installed and active
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Return Refund and Exchange For WooCommerce'. Note the version number displayed.
    Affected if Plugin is installed and version is 4.5.5 or below
  2. Confirm the installed version is vulnerable
    Compare the installed version number against the affected range. The vulnerability affects versions up to 4.5.5. Version 4.5.6 includes the fix.
    Affected if Installed version is 4.5.5 or lower
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the roles assigned. Look for any users with the 'Subscriber' role.
    Affected if At least one user with Subscriber role exists in the system
  4. Verify the API endpoint is accessible
    Check if the wps_rma_fetch_order_msgs AJAX endpoint is accessible. In a default WordPress setup, this would typically be at /wp-admin/admin-ajax.php?action=wps_rma_fetch_order_msgs. An unauthenticated or low-privilege request to this endpoint may indicate exposure.
    Affected if The endpoint responds to requests without proper authorization validation

A user is affected if the plugin version is 4.5.5 or below AND at least one authenticated user with Subscriber-level access or higher exists on the site.

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 the plugin to version 4.5.6 or later which includes proper authorization validation. Until updated, consider restricting subscriber-level account creation or implementing additional access controls at the web application firewall level.

Recommended fix Moderate confidence

Version 4.5.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Return Refund and Exchange For WooCommerce' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. After updating, verify the version number reflects a release higher than 4.5.5
  6. 6. Test that order message retrieval functions correctly for the current user only

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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