# CVE-2021-25003: WPCargo < 6.9.0 - Unauthenticated RCE

> Unauthenticated attackers can upload PHP files to the web server, leading to remote code execution in the WPCargo Track & Trace plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8pgh-m49h-qpxh

## What is CVE-2021-25003?

CVE-2021-25003 is a critical vulnerability in Unknown WPCargo Track & Trace, published on 14 Mar 2022. 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 6.9.0 contains a file which could allow unauthenticated attackers to write a PHP file anywhere on the web server, leading to RCE

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2021-25003?

It affects 1 product.


Products: Wptaskforce Wpcargo Track \& Trace.

## How do I fix CVE-2021-25003?

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

## Is CVE-2021-25003 being exploited?

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

Public exploit code:

- WPCargo < 6.9.0 - Unauthenticated RCE (github_poc): https://github.com/biulove0x/CVE-2021-25003
- WordPress WPCargo Track & Trace <6.9.0 - Remote Code Execution (nuclei): http/cves/2021/CVE-2021-25003.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25003 and fix it if it is affected.

What it is: CVE-2021-25003 is a critical vulnerability in Unknown WPCargo Track & Trace, published on 14 Mar 2022. 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-2021-25003 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-2021-25003/ (Markdown: https://insights.sbomify.com/CVE-2021-25003/index.md)
```

## Sources

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

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