# CVE-2026-28172: WordPress Tracking Code Manager plugin <= 2.6.0 - CSRF to Stored XSS vulnerability

> Unauthenticated attackers can exploit CSRF to inject stored XSS payloads, potentially compromising user sessions and site integrity.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-m77r-w43m-5w96

## What is CVE-2026-28172?

CVE-2026-28172 is a high-severity vulnerability in Data443 Risk Mitigation, Inc. Tracking Code Manager, published on 6 Aug 2026. 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

Unauthenticated Cross Site Request Forgery (CSRF) in Tracking Code Manager <= 2.6.0 versions.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-28172 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28172 is a high-severity vulnerability in Data443 Risk Mitigation, Inc. Tracking Code Manager, published on 6 Aug 2026. 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-2026-28172 in the wild and no public exploit code.

Affected product: Data443 Risk Mitigation, Inc. Tracking Code Manager. 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-28172/ (Markdown: https://insights.sbomify.com/CVE-2026-28172/index.md)
```

## Sources

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

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