dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-31553

CRITICAL · 9.3 CVSS v3.1 Published 2025-04-01
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 WPFactory Advanced WooCommerce Product Sales Reporting webd-woocommerce-advanced-reporting-statistics allows SQL Injection.This issue affects Advanced WooCommerce Product Sales Reporting: from n/a through <= 4.1.1.

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

SQL injection vulnerability in the WPFactory Advanced WooCommerce Product Sales Reporting plugin (webd-woocommerce-advanced-reporting-statistics) allows attackers to inject malicious SQL commands via unsanitized user input in affected versions up to and including 4.1.1. The critical CVSS score of 9.3 indicates the vulnerability is easily exploitable and can lead to complete database compromise.

MitigationUpdate the plugin to the latest version which should contain proper input validation and prepared statements, or implement parameterized queries/prepared statements for all database interactions in the affected code paths to neutralize SQL injection vectors.

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. Verify the plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'webd-woocommerce-advanced-reporting-statistics' or containing 'woocommerce-advanced-reporting'
    Affected if The plugin folder 'webd-woocommerce-advanced-reporting-statistics' or similar WPFactory reporting plugin is found in the WordPress plugins directory
  2. Identify the installed plugin version
    In WordPress admin > Plugins, locate the WPFactory Advanced WooCommerce Product Sales Reporting plugin and read the version number from the plugin description, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The reported version number is 4.1.1 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify the plugin status shows as 'Active' under the plugin name
    Affected if The plugin is currently active and accessible on the site
  4. Check if the reporting feature is accessible
    Attempt to access the plugin's reporting pages via the WordPress admin menu (usually under WooCommerce > Product Sales Reports or similar), or check if the endpoint /wp-admin/admin-ajax.php or custom reporting URLs are reachable
    Affected if The reporting interface or its AJAX handlers are accessible without authentication restrictions
  5. Review plugin source for user input in SQL queries
    If file access is available, inspect PHP files in the plugin directory for direct SQL queries (using $wpdb->prepare, $wpdb->query, or similar) that accept $_GET, $_POST, or $_REQUEST parameters without sanitization
    Affected if Unsanitized user-supplied input (from $_GET, $_POST, $_REQUEST) is found being used in database queries within the plugin code

A user is affected if the WPFactory Advanced WooCommerce Product Sales Reporting plugin is installed with version 4.1.1 or lower, is active, and the vulnerable code path handling unsanitized user input is accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version which should contain proper input validation and prepared statements, or implement parameterized queries/prepared statements for all database interactions in the affected code paths to neutralize SQL injection vectors.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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