WooCommerce <= 2.3.10 - PHP Object Injection
Strategic Overview
- Status
- Patched in 2.3.11
- Affected Plugin
- WooCommerce
- Affected Version
<= 2.3.10- CVSS
- 7.5High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE pending
At a glance
This record tracks a high-severity Deserialization of Untrusted Data vulnerability in the WooCommerce WordPress plugin, affecting versions <= 2.3.10. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). The issue is fixed in version 2.3.11; sites on affected versions should update now. Disclosed June 2015.
Vulnerability Overview
The WooCommerce plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 2.3.10 via deserialization of untrusted input from the $custom parameter. This allows authenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to exploit XXE and read sensitive files from the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in WooCommerce <= 2.3.10 takes a caller who can reach the endpoint. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For WooCommerce the fix is 2.3.11: builds <= 2.3.10 are affected, anything from 2.3.11 onward is not.
Remediation
Update to version 2.3.11, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WooCommerce 2.3.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- 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.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