dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-48122

CRITICAL · 9.3 CVSS v3.1 Published 2025-06-09
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 Holest Engineering Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light excel-like-price-change-for-woocommerce-and-wp-e-commerce-light allows SQL Injection.This issue affects Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light: from n/a through <= 2.4.37.

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 SQL Injection vulnerability exists in the Spreadsheet Price Changer for WooCommerce plugin (versions <= 2.4.37) where user-supplied input is not properly sanitized before being used in SQL queries. An attacker could exploit this by injecting malicious SQL statements through unprotected input fields, potentially gaining unauthorized access to the database, exfiltrating sensitive data, or modifying application data.

MitigationUpgrade the plugin to a patched version as soon as one becomes available. In the interim, restrict access to the affected plugin's administrative interfaces and implement WAF rules to detect and block SQL injection attempts.

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 plugin installation
    Confirm whether the Spreadsheet Price Changer for WooCommerce plugin is installed in your WordPress environment. This can be done through the WordPress admin dashboard under Plugins, or by checking the plugins directory for a folder related to spreadsheet price changing functionality.
    Affected if The plugin is present in the WordPress installation
  2. Check installed version
    Retrieve the plugin version number from the plugin header in the main plugin file, or view it in the WordPress admin dashboard plugin list. Compare this version against the affected range: versions 2.4.37 and earlier.
    Affected if The installed version is 2.4.37 or lower
  3. Audit plugin input handling
    Identify which plugin features accept user-supplied input (such as price import fields, spreadsheet data upload, or settings inputs) and determine if those inputs are processed directly in SQL queries without proper sanitization.
    Affected if User input fields in the plugin are used to construct SQL queries without parameterized preparation
  4. Review for exploitation indicators
    Examine WordPress debug logs, server access logs, and database activity for suspicious SQL syntax, unusual query patterns, or evidence of SQL injection attempts targeting the plugin endpoints.
    Affected if Logs show malformed SQL statements or unexpected database queries originating from plugin functionality

You are affected if the Spreadsheet Price Changer for WooCommerce plugin is installed and its version is 2.4.37 or lower, since the vulnerability exists in how user input is handled in SQL queries.

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

Upgrade the plugin to a patched version as soon as one becomes available. In the interim, restrict access to the affected plugin's administrative interfaces and implement WAF rules to detect and block SQL injection attempts.

Recommended fix Moderate confidence

Latest available version on WordPress plugin repository (vendor should have released a version newer than 2.4.37 with the fix)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light'
  4. 4. Check if an update is available and update to the latest version
  5. 5. If no update is visible in WordPress, visit the official WordPress plugin repository or contact the vendor directly to obtain the latest secure version
  6. 6. Verify the update was successful and test the plugin functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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