CVE-2025-12881

Return Refund and Exchange For WooCommerce <= 4.5.5 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Order Message Read

2025-11-20 18:56
Powpy

Strategic Overview

Status
Patched in 4.5.6
Affected Plugin
Return Refund and Exchange For WooCommerce
Affected Version
<= 4.5.5
CVSS
5.4Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-12881
View all Return Refund and Exchange For WooCommerce vulnerabilities

At a glance

CVE-2025-12881 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Return Refund and Exchange For WooCommerce WordPress plugin, affecting versions <= 4.5.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.5.6; sites on affected versions should update now. Disclosed November 2025, reported by Powpy.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Return Refund and Exchange For WooCommerce <= 4.5.5 carries this weakness at wps_rma_fetch_order_msgs(), and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Return Refund and Exchange For WooCommerce the fix is 4.5.6: builds <= 4.5.5 are affected, anything from 4.5.6 onward is not.

Remediation

Update to version 4.5.6, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Return Refund and Exchange For WooCommerce 4.5.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12881https://www.wordfence.com/threat-intel/vulnerabilities/id/9c159237-1a3a-4d42-9a2e-fbd6ca98f38ehttps://nvd.nist.gov/vuln/detail/CVE-2025-12881

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C