dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47460

HIGH · 7.6 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 TrackShip TrackShip for WooCommerce trackship-for-woocommerce allows SQL Injection.This issue affects TrackShip for WooCommerce: from n/a through <= 1.9.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 TrackShip for WooCommerce plugin (versions <= 1.9.1) allows attackers to inject malicious SQL commands through unsanitized user input processed by the plugin, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate TrackShip for WooCommerce to version > 1.9.1 which includes proper input sanitization and prepared statements; alternatively, disable the plugin until patched.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 TrackShip for WooCommerce plugin installation
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/trackship-for-woocommerce/ directory via file system or FTP
    Affected if The plugin directory exists and the plugin is present in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, find TrackShip for WooCommerce in the plugins list and read the version number displayed beneath the plugin name; alternatively, check the main plugin file (e.g., trackship-for-woocommerce.php) for the 'Version' header comment
    Affected if The version number is 1.9.1 or lower (e.g., 1.9.0, 1.8.5, 1.7.0, etc.)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm the TrackShip for WooCommerce plugin shows as 'Active'
    Affected if The plugin is active and processing requests; even if installed but inactive, the vulnerability is not exploitable in the running environment
  4. Identify plugin endpoints handling user input
    Inspect the plugin code for functions processing $_GET, $_POST, or $_REQUEST parameters that interact with the database without prepared statements; common entry points include AJAX actions (admin-ajax.php) or front-facing tracking pages
    Affected if Any user-supplied input (tracking numbers, order IDs, customer data) is being passed directly to SQL queries without sanitization or prepared statements

Your environment is affected if TrackShip for WooCommerce is installed, active, and running version 1.9.1 or lower while handling user-supplied input through the plugin's database-facing features.

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 TrackShip for WooCommerce to version > 1.9.1 which includes proper input sanitization and prepared statements; alternatively, disable the plugin until patched.

Recommended fix Moderate confidence

Latest version of TrackShip for WooCommerce after 1.9.1

  1. Check the WordPress admin dashboard for available updates to the TrackShip for WooCommerce plugin
  2. Update TrackShip for WooCommerce to the latest available version beyond 1.9.1
  3. Verify the update was applied successfully
  4. Test that the plugin functionality remains operational after the update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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