Tracking Code Manager vulnerabilities
Plugin slug tracking-code-manager · 8 known vulnerabilities · latest disclosed 2026-10-14 · WordPress.org page
Every listed vulnerability has a fix. Version 2.7.0 or later is not affected by any of them. If your site runs an older version, update it.
1 of 8 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Tracking Code Manager
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 6.1 | <= 2.6.0 | 2.7.0 | CVE-2026-15180 | 2026-10-14 | Advisory |
| Medium 4.3 | <= 2.6.0 | 2.7.0 | CVE-2026-28172 | 2026-08-05 | Advisory |
| Medium 6.4 | <= 2.3.0 | 2.4.0 | CVE-2024-8721 | 2024-12-23 | Advisory |
| Medium 4.4 | <= 2.2.0 | 2.3.0 | CVE-2024-6335 | 2024-06-03 | Advisory |
| Medium 4.3 | <= 2.1.0 | 2.2.0 | CVE-2024-31347 | 2024-04-05 | Advisory |
| Medium 4.4 | <= 2.0.16 | 2.1.0 | CVE-2024-2579 | 2024-03-18 | Advisory |
| Medium 6.1 | <= 1.11.4 | 1.11.5 | none | 2017-05-10 | Advisory |
| High 7.5 | <= 1.11.4 | 1.11.5 | none | 2017-05-10 | Advisory |
Check if a site is affected
Enter a site address to see which version of Tracking Code Manager and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Tracking Code Manager plugin safe to use?
All 8 known issues are fixed in current versions (2.7.0 or later). Keeping it updated is what matters.
How do I check which version of Tracking Code Manager my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.