tracking code manager vulnerabilities and fixes
Recent CVEs affecting tracking code manager, with upgrade or downgrade steps. 2 tracked.
Also searched as: trackingcodemanager.
tracking code manager has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2025-05-15. Highest priority: CVE-2024-10309 (score 30/100).
- CVE-2024-6335 MEDIUM 4.8 UPGRADE The Tracking Code Manager WordPress plugin before 2.3.0 does not sanitise and escape some of its settings, whi
- CVE-2024-10309 MEDIUM 5.9 UPGRADE The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox setti
FAQ
How do I fix tracking code manager vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is tracking code manager being exploited right now?
None of the tracked tracking code manager CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tracking code manager CVE should I patch first?
CVE-2024-10309 currently ranks highest (30/100): The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox setti.