Product Filter for WooCommerce by WBW
woo-product-filter · plugin
Known security vulnerabilities for Product Filter for WooCommerce by WBW. Find out in seconds which version runs on your site with WP Lens.
10 known vulnerabilities
2 critical · 8 exploitable without logging in · latest Sep 23, 2026
Listed on wordpress.org · latest 3.4.5 · last updated Sep 21, 2026 · 50K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.3
CVE-2026-95601unauthenticated≤ 3.1.7
WordPress Product Filter by WBW plugin <= 3.1.7 - SQL Injection vulnerability
- Critical 9.3
CVE-2026-39494unauthenticated≤ 3.1.2
WordPress Product Filter by WBW plugin <= 3.1.2 - SQL Injection vulnerability
- High 7.6
CVE-2024-49691high privilege≤ 2.7.0
WordPress Product Filter by WBW plugin <= 2.7.0 - SQL Injection vulnerability
- High 7.5
CVE-2025-8416unauthenticated≤ 2.9.7
Product Filter by WBW <= 2.9.7 - Unauthenticated SQL Injection
- High 7.5
CVE-2025-2317unauthenticated≤ 2.7.9
Product Filter by WBW <= 2.7.9 - Unauthenticated SQL Injection via filtersDataBackend Parameter
- High 7.3
CVE-2021-4444unauthenticated≤ 1.4.9
Product Filter by WooBeWoo <= 1.4.9 - Missing Authorization
- Medium 6.5
CVE-2026-3138unauthenticated≤ 3.1.2
Product Filter for WooCommerce by WBW <= 3.1.2 - Missing Authorization to Unauthenticated Filter Data Deletion via TRUNCATE TABLE
- Medium 6.1
CVE-2026-7804unauthenticated · needs a click≤ 3.4.2
Product Filter for WooCommerce by WBW <= 3.4.2 - Reflected Cross-Site Scripting via 'wpf_fid' Parameter
- Medium 5.3
CVE-2025-11269unauthenticated≤ 3.0.0
Product Filter by WBW <= 3.0.0 - Missing Authorization to Unauthenticated Settings Update
- Medium 4.3
CVE-2023-50877login required≤ 2.5.0
WordPress Product Filter by WBW plugin <= 2.5.0 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).