# CVE-2026-12713: WPCargo Track & Trace < 8.0.4 - Unauthenticated SQL Injection via wpcargo_tracking_number

> Unauthenticated attackers can perform SQL injection attacks via the wpcargo_tracking_number parameter in the WPCargo Track & Trace plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-c29x-63cj-8wmw

## What is CVE-2026-12713?

CVE-2026-12713 is a critical SQL injection vulnerability in Unknown WPCargo Track & Trace, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-12713?


## How do I fix CVE-2026-12713?

No fix has been published for CVE-2026-12713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12713 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12713 and fix it if it is affected.

What it is: CVE-2026-12713 is a critical SQL injection vulnerability in Unknown WPCargo Track & Trace, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12713 exists.

Affected product: Unknown WPCargo Track & Trace. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12713/ (Markdown: https://insights.sbomify.com/CVE-2026-12713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12713
- OSV: https://osv.dev/vulnerability/CVE-2026-12713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12713/
Summaries are generated and may contain mistakes; the official description above is the record.