Skip to main content
CVE-2026-88942VulnerabilityPublished

The Product Filter for WooCommerce by WBW plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-88942· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium.

Data as of 31 Oct 2026, 10:39 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
woobewooProduct Filter for WooCommerce by WBWAffected
  • <=3.4.6
Fixed in–

AI-suggested

Until a fix is available, users should exercise caution with untrusted input and consider disabling or restricting use of the affected plugin. Monitor vendor channels for updates and apply patches promptly once released.

Description

The Product Filter for WooCommerce by WBW plugin for WordPress contains a reflected cross-site scripting (XSS) vulnerability via the 'wpf_fid' JSON parameter in all versions up to and including 3.4.6. The flaw is due to insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts that execute when a user interacts with crafted content. The vulnerability remains in versions patched at 3.4.3 because the sanitization was incomplete, leaving the JSON-decoded filterSettings payload unsanitized.

References

Community reviews

Loading reviews…