dbcve.org
Track \& TraceWordPress extension · Wptaskforce

CVE-2024-44004

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to after 7.0.6 or later.
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 Arni Cinco WPCargo Track & Trace wpcargo allows SQL Injection. This issue affects WPCargo Track & Trace: before 8.0.4.

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 WPCargo Track & Trace WordPress plugin versions 8.0.2 and earlier allows attackers to inject malicious SQL queries via unsanitized user input in the plugin's database interactions, potentially enabling unauthorized data access or manipulation.

MitigationUpdate WPCargo Track & Trace to the latest version that patches this vulnerability, or apply parameterized query/prepared statement fixes to the vulnerable plugin code to properly neutralize SQL special characters in user-supplied input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Track \& TraceWordPress extension
Affected:<= 7.0.6

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 WPCargo/Wptaskforce Track & Trace plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Track & Trace plugin. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag, typically found in the plugin's root directory (e.g., wp-content/plugins/wptaskforce-track-and-trace/wptaskforce-track-and-trace.php)
    Affected if The displayed version is 8.0.2 or earlier, or for the Wptaskforce variant, 7.0.6 or earlier
  2. Confirm the plugin is active
    In WordPress admin, verify that the Track & Trace plugin shows as 'Active' in the Plugins list. A deactivated plugin with a vulnerable version does not expose the vulnerability since the vulnerable code is not executing
    Affected if The plugin is active and the version falls within the affected range
  3. Identify if the plugin handles user-supplied tracking inputs
    The vulnerability exists in database interactions where user input is not sanitized. Check if the tracking page or API endpoints that accept user input (such as tracking numbers entered by visitors on the frontend) are accessible and functional
    Affected if The tracking functionality is publicly accessible and accepts user input without sanitization, combined with a vulnerable version number

A user is affected if the WPCargo/Wptaskforce Track & Trace plugin is active and the installed version is within the vulnerable range (8.0.2 or earlier for WPCargo, 7.0.6 or earlier for Wptaskforce), and the plugin's tracking input feature is accessible to users.

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
Upgrade available Upgrade to a release after 7.0.6
Interim mitigation

Update WPCargo Track & Trace to the latest version that patches this vulnerability, or apply parameterized query/prepared statement fixes to the vulnerable plugin code to properly neutralize SQL special characters in user-supplied input.

Recommended fix Moderate confidence

Latest version of WPCargo Track & Trace (version 8.0.3 or higher, as 8.0.2 is the last known vulnerable version)

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate WPCargo Track & Trace (or WPCargo) in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly and test the track and trace functionality.
Caveat Minor or patch updates typically have no breaking changes; always review changelog for any notable changes

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

Fix this in Track \& Trace Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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