WooCommerce Anti-Fraud <= 3.2 - Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 3.3
- Affected Plugin
- WooCommerce Anti-Fraud
- Affected Version
<= 3.2- CVSS
- 5.4Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE pending
At a glance
This record tracks a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WooCommerce Anti-Fraud WordPress plugin, affecting versions <= 3.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 3.3; sites on affected versions should update now. Disclosed November 2020, reported by Brian Henry.
Vulnerability Overview
The WooCommerce Anti-Fraud plugin for WordPress is vulnerable to Insecure Direct Object Reference (IDOR) due to insufficient user validation on the paypal_verification() function in versions up to, and including, 3.2. This makes it possible for unauthenticated attackers to change any user's order status.
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
WooCommerce Anti-Fraud <= 3.2 carries this weakness at paypal_verification(), and reaching it takes a caller who can reach the endpoint. 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 WooCommerce Anti-Fraud the fix is 3.3: builds <= 3.2 are affected, anything from 3.3 onward is not.
Remediation
Update to version 3.3, 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: WooCommerce Anti-Fraud 3.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WooCommerce Anti-Fraud
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C