CVE-2026-3830
Unauthenticated SQL injection in WBW Product Filter for WooCommerce (<3.1.3).
Is CVE-2026-3830 being exploited?
Not confirmed. CVE-2026-3830 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.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-3830?
CVE-2026-3830 is rated High with a CVSS score of 8.6. 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-3830?
Yes. A fix has been recorded for CVE-2026-3830. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-3830 affect?
CVE-2026-3830 affects Product Filter for WooCommerce by WBW (WordPress) plugin, WordPress sites with plugin < 3.1.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-3830?
Upgrade to 3.1.3+; sanitize inputs; monitor DB logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQL injection enables data read/modify via vulnerable plugin parameter.
Immediate action required
- affected< 3.1.3
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.