Skip to main content

Product Filter For Woocommerce By Wbw CVE-2026-3830

| EUVDEUVD-2026-21881 HIGH
SQL Injection (CWE-89)
2026-04-13 WPScan
8.6
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Identify vulnerable WooCommerce site via automated scanning
  2. Delivery
    Send crafted HTTP request with SQL injection payload to product filter endpoint
  3. Exploit
    Inject UNION SELECT query to extract wp_users table
  4. Install
    Retrieve admin password hashes and customer PII
  5. C2
    Crack password hashes offline
  6. Execute
    Authenticate as WordPress admin
  7. Impact
    Install malicious plugin for persistent access
  8. Step 8
    Exfiltrate complete customer and order database

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Product Filter for WooCommerce by WBW plugin versions before 3.1.3 installed and activated on WordPress site. Remote unauthenticated attacker can exploit via crafted HTTP request to vulnerable parameter. No victim interaction required. Default WordPress installations with this plugin are affected.

Impact

Real-world risk is HIGH despite the CVE year suggesting future designation (likely a typo for 2024/2025). The CVSS 8.6 score reflects critical Confidentiality impact (C:H) with Changed scope (S:C), indicating data breach potential beyond the plugin's immediate context. Attack vector is Network-based (AV:N) with Low complexity (AC:L) and no user interaction required (UI:N), making this trivially exploitable. The unauthenticated attack surface (PR:N) is the most concerning factor-any internet-facing WooCommerce site with this plugin installed is vulnerable without requiring any login. Publicly available exploit code dramatically lowers the skill barrier for mass exploitation. WooCommerce databases typically contain high-value data including customer PII, payment records, and admin credentials, making this an attractive target for credential stuffing, financial fraud, and data theft. The WordPress ecosystem's prevalence and automated scanning tools mean vulnerable instances will be rapidly identified and exploited. This should be treated as a critical-priority patch deployment, particularly for any e-commerce sites processing real transactions.

Exploit ScenarioDerived

An unauthenticated attacker identifies a WooCommerce site running the vulnerable plugin by browsing to the product catalog and observing the filter interface. They craft a malicious HTTP request to the plugin's filter endpoint, injecting SQL commands into the unsanitized parameter, such as a UNION-based injection to extract wp_users table contents. The attacker retrieves administrator password hashes, customer email addresses, order histories, and payment metadata, which they then use for account takeover, credential stuffing attacks against other services, or sale on dark web marketplaces.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 13, 2026

SQL injection in Product Filter for WooCommerce by WBW plugin versions below 3.1.3 allows unauthenticated remote attackers to extract sensitive database contents including user credentials, customer data, and order information. The vulnerability requires no authentication (CVSS PR:N) and has low attack complexity with publicly available exploit code. EPSS data not available, but the combination of unauthenticated access, public POC, and WordPress's large attack surface creates substantial real-world risk for unpatched WooCommerce installations.

RemediationAI

Immediately upgrade the Product Filter for WooCommerce by WBW plugin to version 3.1.3 or later through the WordPress admin dashboard (Plugins > Installed Plugins > Update) or via manual download from the WordPress plugin repository. Version 3.1.3 contains the necessary input sanitization and SQL query parameterization fixes to prevent injection attacks. For sites that cannot immediately patch, temporary mitigation includes disabling the plugin entirely until upgrade is possible, though this will break product filtering functionality. Do not attempt to implement custom input filtering as a workaround-proper parameterized queries in the upstream code are required. After patching, review database access logs for suspicious queries containing UNION, SELECT, or encoded SQL commands in product filter parameters to identify potential prior exploitation. Consult the WPScan advisory at https://wpscan.com/vulnerability/768014fd-0403-4182-b19e-3d46c92d8755/ for additional technical details and indicators of compromise.

Affected VersionsENISA

Product Filter for WooCommerce by WBW 0 <3.1.3

Affected Packages

euvd product_filter_for_woocommerce_by_wbw fix: 3.1.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a classic SQL injection vulnerability (CWE-89) in a WordPress plugin that extends WooCommerce filtering functionality. The flaw stems from improper input sanitization of a user-controllable parameter that is concatenated directly into a SQL query string without parameterization or adequate escaping. The affected component is the Product Filter for WooCommerce by WBW plugin (cpe:2.3:a:unknown:product_filter_for_woocommerce_by_wbw). SQL injection occurs when untrusted data is inserted into database queries, allowing attackers to manipulate query logic, bypass authentication, extract data, or modify database contents. The unauthenticated nature (PR:N in CVSS vector) indicates the vulnerable parameter is accessible without any WordPress login, likely through a publicly exposed AJAX endpoint or front-end filter interface commonly used in WooCommerce product catalog pages.

Know when Product Filter For Woocommerce By Wbw gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.6 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

6
Analysis Updated
Apr 16, 2026 - 05:57 EUVD-patch-fix
executive summary
Patch available
Apr 16, 2026 - 05:29 EUVD
3.1.3
PoC Detected
Apr 15, 2026 - 15:05 vuln.today
Public exploit code
Patch released
Apr 15, 2026 - 15:05 nvd
Patch available
CVSS changed
Apr 13, 2026 - 13:22 NVD
8.6 (HIGH)
CVE Published
Apr 13, 2026 - 06:00 nvd
HIGH 8.6

DescriptionCVE.org

The Product Filter for WooCommerce by WBW WordPress plugin before 3.1.3 does not sanitize and escape a parameter before using it in a SQL statement, allowing unauthenticated users to perform SQL injection attacks

Executive ViewAI

Why It Matters

Product Filter for WooCommerce by WBW plugin versions below 3.1.3 contains a critical SQL injection vulnerability allowing unauthenticated attackers to extract sensitive database contents including customer credentials, payment data, and order information from affected WooCommerce stores. Any unpatched installation exposes customer PII and transactional data to immediate compromise, creating significant liability and operational risk for e-commerce operations.

Business Impact: Severe
Compensating Controls

Vendor-released patch: version 3.1.3 or later. If immediate patching is not feasible, disable the Product Filter plugin entirely until patch can be applied. Implement Web Application Firewall (WAF) rules to block SQL injection patterns targeting the vulnerable plugin endpoint as interim mitigation only.

Threat Intelligence Overview

EPSS Score
0.0%
Top 86% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

63
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy