Vulnerability in Abandoned Cart Pro for WooCommerce (WordPress plugin) (CVE-2026-97657)
Summary
Vulnerability in Abandoned Cart Pro for WooCommerce (WordPress plugin) (CVE-2026-97657). Successful exploitation can lead to full system takeover. Exploitable via user_email.
Original description
The description as published by the source.
The Abandoned Cart Pro for WooCommerce plugin for WordPress is vulnerable to Authentication Bypass via Malleable Encryption and Bypassable HMAC in all versions up to, and including, 10.8.0. This is due to the use of MAC-free AES-CTR encryption for cart-recovery link tokens — where the 8-byte CTR nonce is carried inside the ciphertext blob and the encryption key is looked up using the attacker-supplied user_email GET parameter — combined with an HMAC nonce check in wcap_email_track_links() that is only enforced when the wcap_nonce parameter is non-empty, allowing complete bypass by omission, and an insecure direct object reference on the decrypted abandoned_id with no ownership verification confirming the cart belongs to the email used for decryption. This makes it possible for unauthenticated attackers who possess a single legitimate cart-recovery link (obtained from their own reminder email) to recover the keystream, forge a ciphertext that decrypts to any victim's cart ID, and trigger a call to wp_set_auth_cookie() for the victim user — achieving full account takeover of any user who has ever abandoned a cart, including administrators. The auto-login feature defaults to enabled and is forced on during plugin upgrades, meaning all affected installations are exploitable without any additional configuration.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-97657 has been found in Abandoned Cart Pro for WooCommerce (WordPress plugin).
Attackers can target a specific entry point like user_email over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Abandoned Cart Pro for WooCommerce (WordPress plugin) CVE-2026-97657" on the vendor's site.
CVE-2026-97657 (Abandoned Cart Pro for WooCommerce (WordPress plugin)) — CWE-639 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: user_email / wcap_nonce / abandoned_id
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Abandoned Cart Pro for WooCommerce (WordPress plugin). Attackers reach the vulnerable code path via user_email without authentication.
Check the vendor advisory for the affected versions of Abandoned Cart Pro for WooCommerce (WordPress plugin). Attack surface: user_email / wcap_nonce / abandoned_id.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Abandoned Cart Pro for WooCommerce (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web tychesoftwares.com
- web tychesoftwares.com
- web security@wordfence.com
- web github.com
- web security@wordfence.com
- web security@wordfence.com