dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2317

HIGH · 7.5 CVSS v3.1 Published 2025-04-04
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 time-based SQL Injection via the filtersDataBackend parameter in all versions up to, and including, 2.7.9 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.7.9 is vulnerable to time-based SQL injection via the filtersDataBackend parameter. The vulnerability stems from insufficient input sanitization and lack of prepared statements in the underlying SQL query, allowing unauthenticated attackers to inject arbitrary SQL queries for data exfiltration.

MitigationUpdate the Product Filter by WBW plugin to version 2.8.0 or later, which implements proper input escaping and prepared statements to remediate the SQL injection vulnerability.

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. Confirm Product Filter by WBW plugin is installed
    Locate the plugin directory in the WordPress plugins folder (wp-content/plugins/) and verify the 'product-filter-wbw' or similar directory exists. Alternatively, query the WordPress database wp_options table for the active_plugins option to see if the plugin is listed.
    Affected if The plugin directory or database entry is found, indicating the plugin is present in the WordPress installation.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually product-filter-wbw.php or similar) and locate the plugin header comment containing 'Version:' followed by a version number. Alternatively, check the plugin's readme.txt file for the Stable tag entry.
    Affected if The version number found is 2.7.9 or lower, placing it within the vulnerable version range.
  3. Verify the plugin is active on the site
    Check the WordPress admin under Plugins > Installed Plugins to confirm Product Filter by WBW is activated. Alternatively, query the wp_options table for the active_plugins serialized array containing the plugin slug.
    Affected if The plugin appears as activated in the WordPress admin or the active_plugins option contains the plugin entry, making the vulnerable code reachable.
  4. Confirm vulnerable parameter is accessible
    Review the plugin source code in the backend filter handler file to locate the filtersDataBackend parameter handling. Check that the code path processes this parameter through the SQL query without prepare() statements.
    Affected if The code review reveals the filtersDataBackend parameter is processed in a SQL query without prepared statements, confirming the vulnerability is present in this installation.

The environment is affected if the Product Filter by WBW plugin is installed, active, and running version 2.7.9 or lower, allowing unauthenticated SQL injection via the filtersDataBackend parameter.

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.8.0 or later, which implements proper input escaping and prepared statements to remediate the SQL injection vulnerability.

Recommended fix High confidence

Version 2.8.0 or later

  1. Log in to the WordPress admin dashboard.
  2. Navigate to Plugins > Installed Plugins.
  3. Locate 'Product Filter by WBW'.
  4. If the current version is 2.7.9 or lower, click 'Update Now' to upgrade to the latest version.
  5. Verify the update to version 2.8.0 or later was successful.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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