Tracking Code Manager Vulnerabilities
The Tracking Code Manager WordPress plugin has 2 known security vulnerabilities. The most recent was disclosed on May 10, 2017. Check whether your site runs an affected version below.
View Tracking Code Manager on WordPress.orgSummary
Latest vulnerability disclosed on May 10, 2017.
Recommendation
WPSentry recommends installing with caution
Use Tracking Code Manager only with care. This plugin has a history of high-severity vulnerabilities — always run the latest version and monitor it for newly disclosed issues.
Is your site affected?
Run a free external scan to detect Tracking Code Manager and 35+ other WordPress security checks — no login or plugin required.
Known Tracking Code Manager vulnerabilities
- high
Tracking Code Manager < 1.11.5 - Denial of Service
Affected versions: <=1.11.4Disclosed May 10, 2017 - medium
Tracking Code Manager < 1.11.5 - Cross-Site Scripting
Affected versions: <=1.11.4Disclosed May 10, 2017
How to stay protected
Update promptly
Keep Tracking Code Manager on its latest release — most vulnerabilities are fixed in newer versions.
Scan regularly
Run an external scan after every update to catch outdated or vulnerable software early.
Monitor continuously
Enable monitoring to get alerted the moment a new issue affects your stack.