Skip to content
Laskyr

CVE-2026-88942: Product Filter for WooCommerce by WBW reflected cross-site scripting (XSS) vulnerability

medium 6.1 published 2026-10-31 · updated 2026-11-02

Fixed in Product Filter for WooCommerce by WBW 3.4.7 (first release after the affected range)

Product Filter for WooCommerce by WBW 3.4.6 and older is affected by this reflected XSS issue. Sites on 3.4.7 or newer are not affected; the latest release is 3.4.8.

Affected versions
3.4.6 and older
Fixed in
3.4.7 *
Latest version
3.4.8
Severity
Medium · CVSS 6.1
Active installs
50,000+
Type
Reflected cross-site scripting (XSS)

* The source does not name a fixed version; this is the first wordpress.org release after the last affected version.

What an attacker needs

CVSS vector (score by Wordfence): CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

What to do now

  1. Update Product Filter for WooCommerce by WBW to 3.4.7 or newer (the latest is 3.4.8): Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. Not sure which version you run? Check your version against every known Product Filter for WooCommerce by WBW issue. With WP-CLI: wp plugin get woo-product-filter --field=version.
  5. If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

The advisory

The Product Filter for WooCommerce by WBW plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via 'wpf_fid' JSON Parameter in all versions up to, and including, 3.4.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The vulnerability persists in versions that received the 3.4.3 patch because absint() was applied only to the getVar() read path, leaving the wpf_fid value read from the JSON-decoded filterSettings payload entirely unsanitized.

Description from the CVE record, published by Wordfence (the CVE Numbering Authority), via the NVD entry for CVE-2026-88942.

References

Related

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit