dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-8416

HIGH · 7.5 CVSS v3.1 Published 2025-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 by WBW plugin for WordPress is vulnerable to SQL Injection via the 'filtersDataBackend' parameter in all versions up to, and including, 2.9.7. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 by WBW WordPress plugin versions up to 2.9.7 contains an unauthenticated SQL Injection vulnerability in the 'filtersDataBackend' parameter. The plugin fails to properly escape user input and does not use prepared statements, allowing attackers to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate the Product Filter by WBW plugin to version 2.9.8 or later. As an immediate workaround, consider deploying a WAF rule to block requests containing suspicious SQL patterns in the filtersDataBackend parameter.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify Product Filter by WBW plugin is installed
    Check the WordPress plugins directory for 'product-filter-by-wbw' folder, or query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%product-filter-by-wbw%';
    Affected if The plugin folder or active_plugins entry is not found, meaning the plugin is not installed.
  2. Retrieve installed plugin version
    Read the main plugin file header in wp-content/plugins/product-filter-by-wbw/product-filter.php or query: SELECT option_value FROM wp_options WHERE option_name LIKE '%product_filter_by_wbw%version%';
    Affected if Unable to locate the plugin version - it may not be installed.
  3. Compare version against affected range
    Compare the retrieved version number to the affected range: versions 2.9.7 and below are vulnerable. Example: if version is 2.9.7, 2.9.6, 2.9.5, etc., it falls within the affected range.
    Affected if Version is 2.9.7 or earlier - the environment is potentially affected.
  4. Confirm plugin is active
    Check if the plugin is enabled in WordPress by querying the active_plugins option or inspecting the plugins admin page. Unauthenticated SQLi is exploitable when the plugin is active.
    Affected if Plugin is active - the vulnerable parameter is exposed to unauthenticated attackers.

If the Product Filter by WBW plugin is installed, active, and running version 2.9.7 or earlier, the environment is affected by this unauthenticated SQL injection vulnerability.

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 Product Filter by WBW plugin to version 2.9.8 or later. As an immediate workaround, consider deploying a WAF rule to block requests containing suspicious SQL patterns in the filtersDataBackend parameter.

Recommended fix Moderate confidence

Version higher than 2.9.7 (check WordPress plugin repository for latest stable release)

  1. Update the Product Filter by WBW WordPress plugin to the latest available version beyond 2.9.7
  2. After updating, verify the plugin functions correctly on the site
  3. Test the filter functionality to ensure the SQL injection vulnerability is resolved
  4. Consider reviewing the site's access logs for any signs of exploitation attempts prior to patching

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8416 — 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-2025-8416 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