HomeWordPress vulnerabilitiesTracking Code Manager
Tracking Code Manager vulnerabilities
Tracking Code Manager has 3 known vulnerabilities in this database. The most recent published record is dated 15 May 2025.
- Known vulnerabilities
- 3
- Active installs
- 90,000+
- Latest version
- 2.8.0
- Last updated
- 20 Aug 2026
- Most recent
- 15 May 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2024-6335 | Medium 4.8 | Before 2.3.0 | Fixed in 2.3.0 | 15 May 2025 |
| Cross-site scripting (XSS) CVE-2024-10309 | Medium 5.9 | Before 2.4.0 | Fixed in 2.4.0 | 30 Jan 2025 |
| Cross-site scripting (XSS) CVE-2024-8721 | Medium 6.4 | Up to 2.3.0 | Fixed in a later version (latest 2.8.0) | 24 Dec 2024 |
Read the published descriptions
- CVE-2024-6335, 15 May 2025
- The Tracking Code Manager WordPress plugin before 2.3.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-10309, 30 Jan 2025
- The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox settings when outputing them in the page, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks. CVE record
- CVE-2024-8721, 24 Dec 2024
- The Tracking Code Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the tracking code field in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE-2024-10309 is a duplicate of this issue. CVE record
What to do if you run Tracking Code Manager
If you run Tracking Code Manager, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Tracking Code Manager vulnerabilities
Free. We email you when a new vulnerability is published for Tracking Code Manager, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.