Skip to content
Web

CVE-2026-66682

9.8
Critical
EPSS 0.33%Patch availableAug 22, 2026

Unauthenticated privilege escalation in Abandoned Cart Pro for WooCommerce <=10.4.0

common questions

Is CVE-2026-66682 being exploited?

Not confirmed. CVE-2026-66682 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-66682?

CVE-2026-66682 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-66682?

Yes. A fix has been recorded for CVE-2026-66682. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-66682 affect?

CVE-2026-66682 affects Abandoned Cart Pro for WooCommerce <= 10.4.0, WordPress sites running WooCommerce with the plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66682?

Update Abandoned Cart Pro to fixed version (>10.4.0); rotate admin creds and audit logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Abandoned Cart Pro for WooCommerce <= 10.4.0WordPress sites running WooCommerce with the plugin installed
impact

Unauthenticated attackers can escalate to administrative privileges on affected WordPress/WooCommerce sites, enabling site takeover, data theft, or malicious plugin actions.

action required

Immediate action required

affected versions
Tyche Softwares. Abandoned Cart Pro for WooCommerce
  • affected<= 10.4.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free