WooCommerce < 6.3.1 - Unauthorized Order Status Change
Strategic Overview
- Status
- Patched in 3.5.10
- Affected Plugin
- WooCommerce
- Affected Version
3.5 – < 6.3.1 · 29 branches- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the WooCommerce WordPress plugin, affecting versions 3.5 – < 6.3.1 · 29 branches. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.5.10; sites on affected versions should update now. Disclosed March 2022.
Vulnerability Overview
The WooCommerce plugin for WordPress is vulnerable to authorization bypass due to a missing capability check and nonce check on the PayPal order updates functionality in versions up to, and including, 6.3.0. This makes it possible for authenticated attackers to change the status of arbitrary orders that have been created with PayPal.
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-862: Missing Authorization
Reaching this weakness in WooCommerce 3.5 – < 6.3.1 · 29 branches takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WooCommerce the fix is 3.5.10: builds 3.5 – < 6.3.1 · 29 branches are affected, anything from 3.5.10 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.5.10, 3.6.7, 3.7.3, 3.8.3, 3.9.5, 4.0.4, 4.1.4, 4.2.5, 4.3.6, 4.4.4, 4.5.5, 4.6.5, 4.7.4, 4.8.3, 4.9.5, 5.0.3, 5.1.3, 5.2.5, 5.3.3, 5.4.4, 5.5.4, 5.6.2, 5.7.2, 5.8.1, 5.9.1, 6.0.1, 6.1.2, 6.2.2, 6.3.1
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 3.5.10 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WooCommerce
- 8.8CVE-2021-32790: WooCommerce < 5.5 Blind SQL Injection
CVE-2021-32790 - 8.8WooCommerce <= 4.0.4 Unauthorized Post Meta Creation/Modification
- 8.8WooCommerce <= 3.6.4 CSRF to Stored Cross-Site Scripting
- 8.8CVE-2017-18356: WooCommerce <= 3.2.3 PHP Object Injection
CVE-2017-18356 - 7.5CVE-2026-48888: WooCommerce < 11.1.0 Denial of Service
CVE-2026-48888 - 7.5WooCommerce <= 2.3.10 PHP Object Injection
- 7.3CVE-2014-6313: WooCommerce <= 2.2.2 Cross-Site Scripting
CVE-2014-6313 - 7.2WooCommerce <= 6.2.0 Path Traversal via Tax Importer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C