CVE-2026-28172: Tracking Code Manager · CSRF
Source GCVE Database
Not known to be exploited · CVSS 7.1 High.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Data443 Risk Mitigation, Inc.Tracking Code Manager | Affected
| Fixed in– |
AI-suggested
Until a fix is available, users should consider implementing CSRF protections such as verifying origin headers or using anti-CSRF tokens if possible.
Description
CVE-2026-28172 is a high-severity vulnerability in Tracking Code Manager versions up to and including 2.6.0. It allows unauthenticated attackers to perform Cross Site Request Forgery (CSRF) attacks, potentially leading to partial confidentiality, integrity, and availability impacts.