Product Filter by WBW ≤ 3.4.6: Unauthenticated Blind SQL Injection in Your Storefront (CVE-2026-112866, CVSS 9.3)

Running Product Filter by WBW on your site? Check it against CVE-2026-112866 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Product Filter by WBW is in the affected range (≤ 3.4.6), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Product Filter by WBW ≤ 3.4.6: Unauthenticated Blind SQL Injection in Your Storefront (CVE-2026-112866, CVSS 9.3)

If you run a WooCommerce store, the product filter is the one widget every visitor touches — it sits on your shop pages and takes input from people who haven't logged in, because that's its job. In Product Filter by WBW, that input reaches the database unsafely in every version up to 3.4.6.

What Happened

CVE-2026-112866 is an unauthenticated blind SQL injection in Product Filter by WBW (WPFactory), disclosed by Patchstack on October 22, 2026.

What's in a WooCommerce database worth injecting for? Customer records, order history, email addresses, and the credential hashes that turn one store's breach into password-reuse attacks everywhere else.

Am I Affected?

Check the version your site announces — the plugin's public readme discloses it, which is how our free mini-scan flags affected sites. In wp-admin: Plugins → Installed Plugins → Product Filter by WBW. At or below 3.4.6, you're in range.

What To Do Now

  1. Update to 3.4.7 or later.
  2. Because the flaw is unauthenticated and storefront-facing, don't stop at the patch. Skim your admin user list and recent orders for anomalies, and rotate WordPress salts if anything looks off. A blind injection leaves quieter traces than a defacement; our guide to checking whether your web app is hacked lists what to look for.
  3. Put storefront plugins on your fastest patch cycle. Anything that renders for anonymous visitors — filters, search, forms — is public attack surface, whatever it does for your conversion rate.

The Bigger Lesson

Storefront plugins inherit the store's data and the public's access. October's WordPress run made the pattern hard to miss — this was one of eleven qualifying disclosures in a single week, several of them in plugins whose whole purpose is accepting input from strangers.

Related: Newsletters Lite: Two Critical Flaws in One Plugin — the week's other unauthenticated SQL injection. WordPress Hardening for AI-Built Sites — user enumeration, xmlrpc, and the rest of the storefront's standing exposure.


Running a Woo store? Run the free check at preshipit.com/free-scan — it reads the Product Filter version your site announces and flags the affected range.

Check Product Filter by WBW on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Product Filter by WBW's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-112866 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Product Filter by WBW on your site? Check it against CVE-2026-112866 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Product Filter by WBW is in the affected range (≤ 3.4.6), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report