Skip to main content

WPCargo Track & Trace CVE-2026-12713

| EUVDEUVD-2026-53734 CRITICAL
SQL Injection (CWE-89)
2026-08-06 WPScan GHSA-c29x-63cj-8wmw
9.1
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running WPCargo plugin
  2. Delivery
    Send crafted request with SQL payload
  3. Exploit
    Injection alters backend query
  4. Execution
    Extract admin hashes and secrets
  5. Impact
    Authenticate and take over site

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires only that a WordPress site have the WPCargo Track & Trace plugin (any version before 8.0.4) installed and active, with its vulnerable request handler reachable over the network - no authentication (PR:N), no user interaction (UI:N), and no non-default configuration are needed per the CVSS vector. The primary limiting factor is deployment scope: the target must be running this specific, relatively niche plugin, and must not already be on 8.0.4+ or behind a WAF filtering SQL injection payloads. Note this is a separate code path from CVE-2024-44004, so sites patched only against that earlier CVE remain exploitable.

Impact

The signals are partially conflicting and warrant nuanced triage. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:N) describes a network-reachable, low-complexity, unauthenticated attack with high confidentiality and integrity impact - a genuinely severe profile, and publicly available exploit code lowers the barrier further. However, EPSS is only 0.18% (7th percentile) and the CVE is absent from CISA KEV, indicating no observed mass exploitation yet. This is consistent with a real but not-yet-widely-weaponised issue: the low EPSS likely reflects the plugin's limited deployment footprint rather than exploitation difficulty. Net assessment: a real, patch-worthy priority for any site running the plugin (unauthenticated SQLi with POC), but not an emergency across the broader internet given the niche product. The A:N rating is appropriate since SQL injection here reads/writes data rather than degrading availability.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP request to the WordPress site with malicious input in the vulnerable parameter, which is concatenated into a backend SQL query. Using UNION-based or blind injection techniques, the attacker extracts administrator password hashes and secret keys from the wp_users and wp_options tables, then cracks or reuses them to gain site control. Public exploit code exists (WPScan), and the low attack complexity (AC:L) with no required authentication or user interaction makes automated exploitation straightforward once a target is identified.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 06, 2026

SQL injection in the WPCargo Track & Trace WordPress plugin before version 8.0.4 allows unauthenticated attackers to inject arbitrary SQL through an improperly sanitised parameter, exposing the WordPress database. Reported by WPScan with publicly available exploit code, this flaw is notable for affecting a code path distinct from the previously patched CVE-2024-44004, indicating an incomplete prior fix. Despite a CVSS 9.1 and public POC, the EPSS score is low (0.18%, 7th percentile) and the CVE is not on CISA KEV, so there is no public exploit identified as actively exploited in the wild.

RemediationAI

Vendor-released patch: upgrade the WPCargo Track & Trace plugin to version 8.0.4 or later, which the vendor has released to fix this specific injection path. Because the flaw is distinct from CVE-2024-44004, sites that only applied the earlier fix remain vulnerable and must update to 8.0.4. If immediate patching is not possible, apply compensating controls: place a WAF rule (e.g., WPScan/Wordfence signatures) to block SQL metacharacters on the vulnerable plugin endpoints, restrict access to the plugin's request handlers via web-server rules, or deactivate the WPCargo Track & Trace plugin entirely until it can be updated (trade-off: disables package-tracking functionality for site users). Review database logs for anomalous queries and rotate WordPress secrets and admin credentials if compromise is suspected. Consult the WPScan advisory (https://wpscan.com/vulnerability/5fecb389-c327-4084-a5c8-61e5098386d6/) for endpoint-specific detail.

Affected VersionsENISA

WPCargo Track & Trace 0 <8.0.4

Affected Packages

euvd wpcargo_track_trace fix: 8.0.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a classic CWE-89 (SQL Injection) in a WordPress shipping/logistics tracking plugin. A user-controlled parameter is concatenated into a SQL statement without proper sanitisation or escaping, so crafted input alters the intended query. Because WordPress plugins execute against the shared MySQL/MariaDB backend hosting all site data (wp_users, wp_options, etc.), a successful injection reaches sensitive tables including password hashes and secret keys. The CPE (cpe:2.3:a:unknown:wpcargo_track_&_trace) confirms the affected component is the WPCargo Track & Trace plugin itself. Critically, the description states this is a separate code path from CVE-2024-44004, meaning the earlier remediation did not cover this injection point.

Know when Wpcargo Track Trace gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 9.1 CRITICAL

Unauthenticated network-reachable SQLi (AV:N/AC:L/PR:N/UI:N) yields high confidentiality and integrity impact via database access; no availability impact, so A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

3
Patch available
Aug 06, 2026 - 07:02 EUVD
CVE Published
Aug 06, 2026 - 06:00 cve.org
CRITICAL 9.1
CVE Published
Aug 06, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The WPCargo Track & Trace WordPress plugin before 8.0.4 does not properly sanitise and escape a parameter before using it in a SQL statement, allowing unauthenticated users to perform SQL injection attacks. This affects a code path distinct from the one addressed by CVE-2024-44004.

Executive ViewAI

Why It Matters

WPCargo Track & Trace WordPress plugin versions before 8.0.4 contain a critical SQL injection vulnerability allowing unauthenticated attackers to access WordPress databases directly. Any organization using this plugin without the latest patch faces risk of customer data exposure, operational record compromise, and system configuration leakage, requiring immediate patching.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
niche WordPress logistics-tracking plugin, limited install base
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

66
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy