Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WooCommerce store with HPOS enabled
-
DeliverySend crafted serialized payload to order endpoint
-
ExploitPlugin unserializes untrusted input
-
ExecutionTrigger gadget chain in bundled dependency
-
ImpactExecute arbitrary PHP as web user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the store to have WooCommerce High-Performance Order Storage (HPOS) enabled - this is the explicit precondition named in the description; without HPOS the vulnerable unserialize path is not reached. The plugin must be a vulnerable version (4.7.0 to below 9.1.0). Given the CVSS vector (PR:N/UI:N), no authentication or user interaction is required once HPOS is active, and the gadget chain must be present in the bundled dependencies (which the advisory states it is). The primary limiting factor is therefore the non-default HPOS configuration; stores still on legacy order storage are not exploitable via this path. |
| Impact | Signals are mostly aligned toward high priority: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, score 9.8) indicates a fully remote, unauthenticated, low-complexity attack with total impact, and the description explicitly says unauthenticated users can reach RCE. Public exploit code exists and EPSS is elevated at 28%, well above baseline, reinforcing that exploitation is plausible in the near term. The key mitigating factor is that exploitation is conditional on High-Performance Order Storage being enabled - a non-universal configuration - so the effective attack surface is narrower than the raw 9.8 suggests. It is NOT in CISA KEV, so despite public POC there is no confirmation of active in-the-wild exploitation. Note the CWE mismatch: CWE-434 (file upload) is recorded, but the described root cause is deserialization/object injection (CWE-502); this should be verified against the WPScan advisory before basing detection rules on the CWE. |
| Exploit ScenarioDerived | An unauthenticated attacker on a WooCommerce store that has HPOS enabled submits a request containing a crafted PHP-serialized payload to an order-processing endpoint. The plugin unserializes it without validation, instantiating a malicious object that triggers a gadget chain in a bundled dependency, executing attacker-supplied PHP on the server. Public exploit code exists, and the low-complexity, no-interaction CVSS profile means the attack can be automated at scale against exposed stores. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 12, 2026
PHP Object Injection escalating to unauthenticated remote code execution affects the WooCommerce Subscriptions WordPress plugin from version 4.7.0 up to (but not including) 9.1.0, but only on stores running WooCommerce's High-Performance Order Storage (HPOS). The plugin unserializes attacker-controlled input without validation, and a gadget chain in bundled dependencies turns that into arbitrary code execution. Publicly available exploit code exists and a vendor patch (9.1.0) is available, but this is not listed in CISA KEV; the EPSS score of 28% is elevated, indicating meaningful exploitation probability.
RemediationAI
Vendor-released patch: upgrade WooCommerce Subscriptions to 9.1.0 or later, which validates input before deserialization; this is the primary and recommended fix. If immediate patching is not possible, a targeted compensating control is to disable High-Performance Order Storage (revert to legacy post-based order storage under WooCommerce > Settings > Advanced > Features), which removes the vulnerable code path - with the trade-off of losing HPOS performance and scalability benefits and requiring a data sync back to legacy tables. As additional interim controls, place the store behind a WAF with rules blocking PHP-serialized object payloads (strings containing patterns like O:<n>: in request bodies) and restrict/monitor the order-handling endpoints, accepting possible false positives on legitimate serialized data. Consult the WPScan advisory (https://wpscan.com/vulnerability/191f76cf-e5bd-4a37-ac1c-9187cea2aa27/) for exact affected paths before deploying request-filtering rules.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WooCommerce Subscriptions is a commercial WordPress/WooCommerce extension that manages recurring billing and subscription orders. The flaw stems from passing untrusted input to PHP's unserialize() - the classic PHP Object Injection (POI) pattern (properly CWE-502, though the record is tagged CWE-434 Unrestricted File Upload, a likely mislabel given the described mechanism). When HPOS is enabled, order data is stored in dedicated custom tables rather than the legacy wp_posts/postmeta structure, and the affected deserialization path is reachable in that mode. Because unserialize() reconstructs arbitrary PHP objects, an attacker who controls the serialized blob can instantiate objects whose magic methods (__wakeup/__destruct) form a 'gadget chain' - here present in the plugin's bundled dependencies - leading to code execution. The CPE cpe:2.3:a:unknown:woocommerce_subscriptions:*:*:*:*:*:*:*:* confirms the affected component but does not bound the version range.
Know when Woocommerce Subscriptions gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated remote object injection to RCE gives AV:N/AC:L/PR:N/UI:N with full C/I/A impact; HPOS is a deployment precondition, not an access barrier, so PR stays N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The WooCommerce Subscriptions WordPress plugin before 9.1.0 does not validate user input before unserializing it on stores with High-Performance Order Storage enabled, leading to a PHP Object Injection issue which unauthenticated users can escalate to Remote Code Execution via a gadget chain present in the bundled dependencies.
Articles & Coverage 1
Executive ViewAI
WooCommerce Subscriptions plugin (versions 4.7.0 through 9.0.x) contains a critical remote code execution vulnerability affecting e-commerce platforms using WooCommerce's High-Performance Order Storage. Unauthenticated attackers can exploit a PHP object injection flaw to gain complete system control, directly compromising customer payment data, order records, and store operations. Publicly available exploit code exists with an estimated 28% exploitation likelihood, representing an immediate threat to revenue continuity and customer data security.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-57100
GHSA-5736-34m2-3cxc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB