dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-48118

HIGH · 8.5 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 WpExperts Hub Woocommerce Partial Shipment wc-partial-shipment allows SQL Injection.This issue affects Woocommerce Partial Shipment: from n/a through <= 3.2.

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

SQL injection vulnerability in WpExperts Hub WooCommerce Partial Shipment plugin (wc-partial-shipment) allows attackers to inject malicious SQL commands through unsanitized input in SQL queries. The vulnerability affects versions up to and including 3.2.

MitigationUpdate to a patched version of the WooCommerce Partial Shipment plugin if available; otherwise, refactor vulnerable database queries to use parameterized queries or prepared statements with proper input sanitization.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 WooCommerce Partial Shipment plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin, or inspect the wp-content/plugins/ directory for a folder named 'wc-partial-shipment' or similar partial shipment plugin for WooCommerce
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the partial shipment plugin to view its version number. Alternatively, check the main plugin PHP file for a 'Version' header comment
    Affected if The installed version is older than the patched version released to address this SQL injection vulnerability
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if the partial shipment plugin is activated. Also verify WooCommerce itself is active, as the plugin requires WooCommerce to function
    Affected if The plugin is activated and handling order/shipment data, which would expose the vulnerable SQL code paths
  4. Inspect database query handling for the plugin
    Review the plugin's PHP files, particularly those handling order retrieval or shipment processing (typically files with names containing 'order', 'shipment', or 'query'), for direct use of $_POST, $_GET, or $_REQUEST variables in SQL queries without prepared statements or escaping
    Affected if The plugin code contains SQL queries that incorporate user input directly without using $wpdb->prepare() or parameterized queries
  5. Review database access logs for suspicious SQL patterns
    Examine MySQL/MariaDB general query log or slow query log (if enabled) for entries from the WordPress database user containing unusual UNION statements, OR 1=1 conditions, or other SQL injection patterns targeting tables related to orders or shipments
    Affected if Logs contain SQL queries from the site that include injection syntax or unexpected logical conditions

The environment is affected if the WooCommerce Partial Shipment plugin is installed and active, with a version prior to the patched release, and the plugin processes user input in SQL queries without proper sanitization.

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 to a patched version of the WooCommerce Partial Shipment plugin if available; otherwise, refactor vulnerable database queries to use parameterized queries or prepared statements with proper input sanitization.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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