CVE-2025-31059
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in woobewoo WBW Product Table PRO woo-producttables-pro allows SQL Injection.This issue affects WBW Product Table PRO: from n/a through <= 2.2.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 confidenceA SQL Injection vulnerability exists in the woobewoo WBW Product Table PRO plugin (versions <= 2.2.6) used with WooCommerce. The vulnerability allows attackers to inject malicious SQL queries through unsanitized user inputs, potentially enabling unauthorized database access, data exfiltration, or data manipulation.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce installationCheck for the presence of WooCommerce plugin in wp-content/plugins/woocommerce/ or via WordPress admin plugins listAffected if WooCommerce is not installed - the vulnerability only affects environments using this e-commerce platform
-
Identify WBW Product Table PRO pluginLook for the plugin folder named 'product-table' or 'wbw-product-table' in wp-content/plugins/ or check WordPress admin under Plugins > Installed PluginsAffected if The WBW Product Table PRO plugin is not found - only installations with this specific plugin are affected
-
Check installed plugin versionOpen the plugin's main PHP file or readme.txt and locate the Version field in the plugin header comment; compare against the vulnerable range <= 2.2.6Affected if The installed version number is 2.2.6 or lower (versions 2.2.6 and below are vulnerable)
-
Confirm plugin is activeIn WordPress admin, verify the WBW Product Table PRO plugin shows as Active, or query the wp_options table for option_name='active_plugins' containing the plugin identifierAffected if The plugin is active and processing requests - the SQL injection vulnerability is reachable when the plugin handles user-supplied input in product table queries
You are affected if WooCommerce is installed with the WBW Product Table PRO plugin at version 2.2.6 or lower, and the plugin is active.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to the latest version of WBW Product Table PRO when available, or implement proper input validation and parameterized queries (prepared statements) for all database interactions within the affected plugin code.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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