Strategic Overview
- Status
- Patched in 10.5.3
- Affected Plugin
- WooCommerce
- Affected Version
< 10.5.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-3589
At a glance
CVE-2026-3589 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce WordPress plugin, affecting versions < 10.5.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.5.3; sites on affected versions should update now. Disclosed March 2026, reported by oolongeya.
Vulnerability Overview
The WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 10.5.3 (exclusive). This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action granted they can trick a site administrator into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WooCommerce < 10.5.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WooCommerce the fix is 10.5.3: builds < 10.5.3 are affected, anything from 10.5.3 onward is not.
Remediation
Update to version 10.5.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WooCommerce 10.5.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- 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.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
- 7.2WooCommerce <= 3.6.4 Missing File Type Validation
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C