WPCargo Track & Trace <= 8.0.3 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Patched in 8.0.4
- Affected Plugin
- WPCargo Track & Trace
- Affected Version
<= 8.0.3- CVSS
- 7.5High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2024-44004
At a glance
CVE-2024-44004 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WPCargo Track & Trace WordPress plugin, affecting versions <= 8.0.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 8.0.4; sites on affected versions should update now. Disclosed September 2024, reported by LVT-tholv2k.
Vulnerability Overview
The WPCargo Track & Trace plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 8.0.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WPCargo Track & Trace <= 8.0.3 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WPCargo Track & Trace the fix is 8.0.4: builds <= 8.0.3 are affected, anything from 8.0.4 onward is not.
Remediation
Update to version 8.0.4, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPCargo Track & Trace 8.0.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WPCargo Track & Trace
- 9.8CVE-2021-25003: WPCargo <= 6.8.9 Remote Code Execution
CVE-2021-25003 - 6.1CVE-2022-1435: WPCargo Track & Trace <= 6.9.4 Admin+ Stored XSS
CVE-2022-1435 - 6.1CVE-2022-1436: WPCargo Track & Trace <= 6.9.4 Reflected XSS
CVE-2022-1436 - 5.3CVE-2026-25401: WPCargo Track & Trace <= 8.0.2 Missing Authorization
CVE-2026-25401 - 4.3CVE-2025-31609: WPCargo Track & Trace <= 8.0.1 IDOR
CVE-2025-31609 - 4.3CVE-2024-54271: WPCargo Track & Trace Authenticated (Subscriber+)
CVE-2024-54271
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C