Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAbandon cart with attacker email
-
DeliveryObtain legitimate AES-CTR token
-
ExploitRecover keystream and forge ciphertext
-
ExecutionInject SQL via 'validate', omit wcap_nonce
-
ImpactAppend queries, exfiltrate database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Target must be a WordPress site running Abandoned Cart Pro for WooCommerce version 10.8.0 or earlier with the abandoned-cart tracking functionality active (default behavior of the plugin). The attacker must be able to abandon a cart using an email address they control to harvest one legitimate AES-CTR token, then exploit the stream cipher's malleability to recover the keystream and forge a ciphertext in the 'validate' parameter. Critically, the request must OMIT the wcap_nonce parameter, because the HMAC integrity check added in 10.4.1 is enforced only when that parameter is present - supplying it would block the forgery. No authentication is required (PR:N), no user interaction, and no non-default configuration is needed; the main limiting factor is the attacker's need to perform the token-harvest and keystream-recovery step rather than a one-shot injection. |
| Impact | This is a genuine priority, not a high-CVSS-but-low-risk paper issue, though it falls short of worst-case. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N = 7.5) indicates remote, unauthenticated, low-complexity exploitation with high confidentiality impact and no integrity/availability impact - consistent with a read-oriented SQL injection used to exfiltrate database contents (WordPress user hashes, customer PII, order data). No EPSS score, no CISA KEV listing, and no POC/exploit-availability signal were supplied in the input, so exploitation status is: no public exploit identified at time of analysis. The notable tension is complexity: the attack is not a trivial single-request injection - it requires first obtaining a legitimate AES-CTR token (by abandoning a cart with an attacker-controlled email), recovering the keystream, and forging a ciphertext, while omitting the wcap_nonce parameter to skip the HMAC check added in 10.4.1. This chain is deterministic and reliable for a competent attacker (hence AC:L is defensible), but it is more involved than a generic SQLi, which realistically narrows exploitation to deliberate attackers rather than opportunistic mass scanners in the immediate term. Net: credible, remotely reachable data-theft vulnerability in a WordPress e-commerce plugin, discovered/reported by Wordfence - treat as a high-priority patch, while noting that the absence of EPSS/KEV/POC data means active-exploitation risk cannot be confirmed from the provided inputs. |
| Exploit ScenarioDerived | An attacker visits a store running a vulnerable version of Abandoned Cart Pro for WooCommerce and abandons a cart using an email address they control, obtaining a legitimate encrypted token. Because AES-CTR is a malleable stream cipher, the attacker recovers the keystream from this known token and forges a ciphertext embedding arbitrary SQL into the 'validate' parameter, omitting wcap_nonce so the HMAC integrity check is never invoked. The appended SQL is executed against the WordPress database, letting the unauthenticated attacker extract sensitive data such as user credentials and customer information. No public exploit was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated SQL injection in Abandoned Cart Pro for WooCommerce (all versions up to and including 10.8.0) allows remote attackers to extract sensitive information from a WordPress site's database by forging the plugin's encrypted 'validate' parameter. The parameter is protected with AES-CTR, a malleable stream cipher, so an attacker who abandons a cart using an email address they control can harvest one legitimate token, recover the keystream, and re-encrypt arbitrary SQL; the HMAC integrity check introduced in 10.4.1 is enforced only when the wcap_nonce parameter is present, and omitting that parameter skips the check entirely. CVSS 3.1 scores this 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), reflecting unauthenticated, remote, confidentiality-only impact; no public exploit code and no confirmed active exploitation were identified at time of analysis, though the attack requires only a token-harvest and keystream-recovery step rather than a one-shot injection.
RemediationAI
No vendor-released patch version is identified in the available advisory data, so the Tyche Softwares changelog (https://www.tychesoftwares.com/docs/docs/abandoned-cart-pro-for-woocommerce-new/changelog-abandoned-cart-pro/) should be monitored for a fixed release and applied immediately once published; the Wordfence entry (https://www.wordfence.com/threat-intel/vulnerabilities/id/a656312d-1ddf-48d5-81bf-180c67b32e39?source=cve) should be re-checked for updated version guidance. Note that upgrading within the 10.4.1-10.8.0 range provides no protection, because the HMAC defense added in 10.4.1 is only enforced when wcap_nonce is present. The most reliable compensating control is to deactivate and remove the plugin until a fixed version ships - the trade-off is a complete loss of abandoned-cart tracking and recovery emails, so this is only acceptable where that capability is expendable. Where the plugin must stay live, deploy a WAF or reverse-proxy rule that rejects any request to the plugin's cart-tracking endpoint carrying a 'validate' parameter without a corresponding wcap_nonce value; this effectively restores the 10.4.1 integrity gate (side effect: any legitimate client or cached JavaScript that omits the nonce will be blocked, so validate against production traffic before enforcing). Layer a second rule that constrains 'validate' to the ciphertext alphabet actually expected (base64/hex only) and rejects SQL metacharacters, comments, and whitespace-heavy payloads in that parameter, accepting that encoding tricks may evade keyword filters and that this is defense in depth rather than a fix. Because the exploit is read-only, also reduce blast radius by confirming the WordPress database account is not over-privileged and by monitoring database logs and slow-query output for anomalous SELECT activity originating from the plugin's endpoints. Finally, treat cart-abandonment records and WooCommerce customer data as potentially exposed, and rotate any secrets or credentials retrievable from the WordPress database.
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
The vulnerability is a classic SQL injection (CWE-89) rooted in insufficient escaping of a user-supplied parameter and the absence of a properly parameterized/prepared statement in the query that consumes the 'validate' value. Abandoned Cart Pro for WooCommerce, by Tyche Softwares, is a WordPress/WooCommerce plugin that tracks cart abandonment and issues tokens to identify carts; the CPE cpe:2.3:a:tyche_softwares:abandoned_cart_pro_for_woocommerce:*:*:*:*:*:*:*:* confirms the plugin itself as the affected component across the full version range. What makes this instance unusual is the cryptographic layer: rather than passing the token in plaintext, the plugin encrypts it with AES-CTR. AES-CTR is a stream cipher, so ciphertext is simply plaintext XOR keystream; an attacker who obtains one valid (plaintext, ciphertext) pair - achievable by triggering an abandonment with an email address under their control - can derive the keystream and then encrypt any payload they choose, producing a ciphertext that decrypts successfully. The integrity control added in version 10.4.1 (an HMAC over the token) is conditional: it is validated only when the wcap_nonce parameter is supplied, so an attacker who simply leaves wcap_nonce out of the request bypasses integrity verification altogether. The net effect is that the injection is not trivially one-shot, but it is fully unauthenticated and requires no non-default configuration, with impact bounded to confidentiality (C:H, I:N, A:N) - i.e., arbitrary read of the WordPress database contents such as WooCommerce order data and user records.
Know when Abandoned Cart Pro For Woocommerce 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:N/A:N
Remotely reachable and unauthenticated (AV:N/PR:N); the token-forge chain is deterministic and reliable so AC:L; read-oriented SQLi yields C:H with no stated integrity or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Abandoned Cart Pro for WooCommerce plugin for WordPress is vulnerable to generic SQL Injection via the 'validate' parameter in all versions up to, and including, 10.8.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. AES-CTR is a malleable stream cipher, so an attacker who obtains one legitimate token by abandoning a cart with an email address they control can recover the keystream and forge a ciphertext carrying arbitrary SQL. The HMAC check added in 10.4.1 is enforced only when the wcap_nonce parameter is present, so omitting the parameter skips it entirely.
Executive ViewAI
Abandoned Cart Pro for WooCommerce, a plugin used by many e-commerce sites, contains an unauthenticated SQL injection vulnerability that could allow attackers to extract sensitive customer and order data from the WordPress database. With no vendor patch available, organizations running this plugin are at risk of data breaches that could lead to regulatory fines, loss of customer trust, and operational disruption. Leadership should prioritize immediate mitigation to protect customer information and maintain business continuity.
No vendor-released patch identified at time of analysis. Interim mitigations: disable the plugin, deploy WAF rules to block exploitation of the 'validate' parameter without 'wcap_nonce', restrict access to wp-admin and database, and monitor for suspicious activity. If disabling is not possible, consider virtual patching via WAF or isolating the affected site.
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
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Related Vulnerabilities in Abandoned Cart Pro for WooCommerce SQLi and Auth Bypass
View all 3The Abandoned Cart Lite for WooCommerce and Abandoned Cart Pro for WooCommerce plugins for WordPress are vulnerable to S
Privilege escalation in Abandoned Cart Pro for WooCommerce (Tyche Softwares) affects all versions up to and including 10
Privilege escalation in the Abandoned Cart Pro for WooCommerce WordPress plugin (all versions through 10.7.1) allows aut
EUVD-2026-100777
GHSA-fwwh-fmqj-qv4w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB