Tracking Code Manager

tracking-code-manager · plugin

Known security vulnerabilities for Tracking Code Manager. Find out in seconds which version runs on your site with WP Lens.

4 known vulnerabilities

1 exploitable without logging in · latest Aug 6, 2026

Listed on wordpress.org · latest 2.8.0 · last updated Aug 20, 2026 · 90K+ installs

wordpress.org status checked on Oct 2, 2026

Vulnerabilities

CVE-2026-28172unauthenticated · needs a click≤ 2.6.0
WordPress Tracking Code Manager plugin <= 2.6.0 - CSRF to Stored XSS vulnerability
High 7.1
CVE-2024-8721contributor+≤ 2.3.0
Tracking Code Manager <= 2.3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting
Medium 6.4
CVE-2024-2579high privilege≤ 2.0.16
WordPress Tracking Code Manager plugin <= 2.0.16 - Cross Site Scripting (XSS) vulnerability
Medium 5.9
CVE-2024-31347login required≤ 2.1.0
WordPress Tracking Code Manager plugin <= 2.1.0 - Broken Access Control vulnerability
Medium 4.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory