# CVE-2022-1436: WPCargo Track & Trace < 6.9.5 - Reflected Cross Site Scripting

> Attackers can execute arbitrary scripts in victim browsers via unsanitized tracking number input in the WPCargo Track & Trace plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5c5x-7wp7-xwgj

## What is CVE-2022-1436?

CVE-2022-1436 is a medium-severity cross-site scripting vulnerability in Unknown WPCargo Track & Trace, published on 16 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WPCargo Track & Trace WordPress plugin before 6.9.5 does not sanitise and escape the wpcargo_tracking_number parameter before outputting it back in the page, which could allow attackers to perform reflected Cross-Site Scripting attacks.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-1436?

It affects 1 product.


Products: Wptaskforce Track \& Trace.

## How do I fix CVE-2022-1436?

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

## Is CVE-2022-1436 being exploited?

There is no known exploitation of CVE-2022-1436 in the wild and no public exploit code.

## Other vulnerabilities in Unknown WPCargo Track & Trace

- [CVE-2024-44004](https://insights.sbomify.com/CVE-2024-44004/): WordPress WPCargo Track & Trace plugin <= 8.0.2 - SQL Injection vulnerability (critical 9.3)
- [CVE-2022-1435](https://insights.sbomify.com/CVE-2022-1435/): WPCargo Track & Trace < 6.9.5 - Admin+ Stored Cross Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1436 and fix it if it is affected.

What it is: CVE-2022-1436 is a medium-severity cross-site scripting vulnerability in Unknown WPCargo Track & Trace, published on 16 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1436 in the wild and no public exploit code.

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-2022-1436/ (Markdown: https://insights.sbomify.com/CVE-2022-1436/index.md)
```

## Sources

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

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