Security readout for executives and security teams
Plain-English summary
A flaw in the WordPress WPCargo Track & Trace plugin could let an unauthenticated internet attacker manipulate database queries. Successful abuse could expose sensitive database information and cause limited service disruption. The supplied CVSS score is 9.3, making this a critical remediation priority for organizations running affected versions.
Executive priority
Treat this as an urgent internet-facing application risk. Identify affected sites immediately and remediate promptly because exploitation requires neither credentials nor user action and may disclose sensitive database information. Escalate any suspicious activity for incident-response review, while avoiding claims of compromise without supporting evidence.
Technical view
CVE-2024-44004 is a CWE-89 SQL injection vulnerability in WPCargo Track & Trace. The supplied vector indicates network access, low complexity, no privileges, no user interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact. The description identifies versions before 8.0.4 as affected.
Likely exposure
Exposure is likely where a WordPress site has WPCargo Track & Trace earlier than 8.0.4 installed, particularly when the site is internet-accessible. The bundle does not identify the vulnerable parameter, endpoint, required plugin configuration, or whether disabling the plugin fully removes exposure.
Exploitation context
The vulnerability appears remotely reachable without authentication or user interaction based on the supplied CVSS vector. However, the bundle reports KEV as false and provides no evidence of active exploitation, public exploit availability, or observed attacks. Absence from KEV does not establish that exploitation is impossible.
Researcher notes
Version evidence is inconsistent: the title says 8.0.2 and earlier, the description says before 8.0.4, and the Patchstack URL names 7.0.6. Use the broader supplied boundary of before 8.0.4 pending vendor confirmation. No vulnerable endpoint, parameter, root-cause detail, patch diff, or exploitation evidence is included.
Mitigation direction
- Inventory WordPress installations for WPCargo Track & Trace and record installed versions.
- Upgrade affected installations to version 8.0.4 or later, consistent with the supplied affected-version statement.
- If immediate upgrading is impossible, disable the plugin and consult current vendor guidance.
- Restrict unnecessary access and increase monitoring until remediation is confirmed.
Validation and detection
- Confirm the plugin version is 8.0.4 or later on every WordPress installation.
- Verify older plugin copies are absent from inactive, staging, backup, and cloned sites.
- Review web, application, and database logs for unusual requests or query errors.
- Confirm business functions still operate after upgrading or disabling the plugin.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-44004 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/wpcargo/vulnerability/wordpress-wpcargo-track-trace-plugin-7-0-6-sql-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.