CVE-2026-32551
Unauthenticated SQL injection in Woo Essential plugin allows DB compromise.
Is CVE-2026-32551 being exploited?
Not confirmed. CVE-2026-32551 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-32551?
CVE-2026-32551 is rated Critical. 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-32551?
Yes. A fix has been recorded for CVE-2026-32551. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32551 affect?
CVE-2026-32551 affects Woo Essential plugin <= 4.3.0, WordPress sites using Woo Essential. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32551?
Update Woo Essential to the latest patched version, restrict access, audit logs/backups.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQLi allowing attackers to read/modify/exfiltrate database contents, corrupt data, and enable further takeover or remote code execution via DB abuse.
Immediate action required
- affected<= 4.3.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.