Quick answers
- Is CVE-2026-96901 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96901 being exploited in the wild.
- How severe is CVE-2026-96901?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- WooCommerce Cart Abandonment Recovery before 2.2.0.
- Is there a fix for CVE-2026-96901?
- Yes: fixed in 2.2.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96901 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-96901?
- Check whether you run WooCommerce Cart Abandonment Recovery at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.2.0
Technical details
The plugin accepts unsigned legacy cart-recovery tokens without verifying their integrity, allowing an unauthenticated attacker with knowledge of a victim's cart session identifier to forge tokens and perform unauthorized actions. The vulnerability is an authentication bypass affecting the cart-recovery mechanism that allows modification of abandoned-cart records. A fix is available in version 2.2.0 and later.
Affected products
- WooCommerce Cart Abandonment Recovery before 2.2.0
Timeline
- 2026-10-19: disclosed
- 2026-10-21: advisory