dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3830

HIGH · 8.6 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Product Filter for WooCommerce by WBW plugin before version 3.1.3 contains a SQL injection vulnerability due to improper sanitization of a parameter before its use in a SQL query. Unauthenticated attackers can exploit this to inject arbitrary SQL code.

MitigationUpdate the plugin to version 3.1.3 or later. If immediate update is not possible, consider restricting access to the affected endpoint via web server configuration or disabling the plugin temporarily.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin version
    Navigate to WordPress admin > Plugins > Product Filter for WooCommerce by WBW and read the version number displayed, or inspect the plugin main file (typically /wp-content/plugins/product-filter-for-woocommerce/includes/class-wbw-pf.php or similar) to find the 'Version' header in the plugin comment block.
    Affected if the displayed version is lower than 3.1.3 (e.g., 3.1.2, 3.1.1, 3.0.x, etc.)
  2. Confirm the plugin is active
    In WordPress admin > Plugins, verify that Product Filter for WooCommerce is currently activated. The vulnerability is only exploitable when the plugin is active.
    Affected if the plugin shows as Activated and the version from step 1 is below 3.1.3
  3. Identify the vulnerable endpoint
    The CVE describes a SQL injection via an unsanitized parameter used in a SQL query. Since the specific parameter name is not disclosed in public advisory details, check your web server access logs for unusual or suspicious query patterns targeting WooCommerce filter endpoints (typically URLs containing /?s=, /?filter=, or custom product filter AJAX endpoints). Review logs for any unexpected SQL syntax in request parameters.
    Affected if unusual SQL-like patterns appear in access logs for requests to product filter functionality, especially from unauthenticated sources
  4. Check for unauthorized database modifications
    Review your WordPress database tables (particularly wp_options, wp_users, and any custom product/order tables) for unexpected entries, modified records, or newly created admin-level user accounts that you did not create. Attackers often use SQL injection to create backdoor accounts.
    Affected if unknown admin accounts exist, or table records show unexpected changes coinciding with the time window the plugin was active on an unpatched version

You are affected if the Product Filter for WooCommerce plugin version is below 3.1.3 AND the plugin is currently active on your WordPress/WooCommerce site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.1.3 or later. If immediate update is not possible, consider restricting access to the affected endpoint via web server configuration or disabling the plugin temporarily.

Recommended fix Moderate confidence

Product Filter for WooCommerce by WBW version 3.1.3

  1. Update the Product Filter for WooCommerce by WBW plugin to version 3.1.3 or later through the WordPress admin dashboard under Plugins > All Plugins, or use wp-cli plugin update product-filter-for-woocommerce

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3830 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3830 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data