dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-39496

CRITICAL · 9.3 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WBW WooBeWoo Product Filter Pro allows SQL Injection.This issue affects WooBeWoo Product Filter Pro: from n/a before 2.9.6.

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 · moderate confidence

A critical SQL Injection vulnerability exists in the WooBeWoo Product Filter Pro WordPress/WooCommerce plugin. The flaw allows attackers to inject malicious SQL commands through unsanitized input parameters in the plugin's filter functionality. With a CVSS score of 9.3, this vulnerability is likely exploitable without authentication and could lead to complete database compromise.

MitigationUpdate WooBeWoo Product Filter Pro to version 2.9.6 or later to remediate this vulnerability. Prior to updating, ensure a complete backup is taken and test the update in a staging environment to verify filter functionality remains intact.

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
Low

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

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 WooBeWoo Product Filter Pro plugin version
    In WordPress admin dashboard, go to Plugins > Installed Plugins and find 'WooBeWoo Product Filter Pro' in the list. The version number is displayed below the plugin name.
    Affected if Version number shown is lower than 2.9.6 (for example, 2.9.5, 2.9.4, etc.)
  2. Confirm the plugin is currently active
    In the same Plugins list, verify that 'WooBeWoo Product Filter Pro' shows as 'Active' under the status column, or check Plugins > Add New > Upload Plugin to verify installation.
    Affected if The plugin is activated on the WordPress site
  3. Check for the specific vulnerability exposure
    Review the plugin settings pages (usually under Products > Product Filter or a dedicated filter settings menu) to see which filter parameters are exposed, particularly any that accept user input for database queries.
    Affected if Filter functionality that accepts user-supplied input is enabled and accessible without additional authentication

The environment is affected if WooBeWoo Product Filter Pro version is below 2.9.6 and the plugin is active with user-facing filter functionality enabled.

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 WooBeWoo Product Filter Pro to version 2.9.6 or later to remediate this vulnerability. Prior to updating, ensure a complete backup is taken and test the update in a staging environment to verify filter functionality remains intact.

Recommended fix High confidence

2.9.6

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate WooBeWoo Product Filter Pro in the plugins list
  4. 4. Check the current installed version to confirm it is below 2.9.6
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.9.6
  6. 6. If no automatic update appears, manually download version 2.9.6 from the official WordPress plugin repository or vendor
  7. 7. Deactivate the current plugin, then delete it, then upload and install the new version
  8. 8. After updating, verify the plugin is functioning correctly and test the product filter functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.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-39496 — 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-39496 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