HomeWordPress vulnerabilitiesStatCounter
StatCounter vulnerabilities
StatCounter has 3 known vulnerabilities in this database. The most recent published record is dated 29 May 2026.
- Known vulnerabilities
- 3
- Active installs
- 70,000+
- Latest version
- 2.2.0
- Last updated
- 19 Aug 2026
- Most recent
- 29 May 2026
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-2026-6275 | Medium 6.4 | Up to 2.1.1 | Fixed in a later version (latest 2.2.0) | 29 May 2026 |
| Cross-site scripting (XSS) CVE-2025-13048 | Medium 6.4 | Up to 2.1.0 | Fixed in a later version (latest 2.2.0) | 19 Feb 2026 |
| Cross-site scripting (XSS) CVE-2021-24920 | Medium 4.8 | Before 2.0.7 | Fixed in 2.0.7 | 28 Feb 2022 |
Read the published descriptions
- CVE-2026-6275, 29 May 2026
- The StatCounter - Free Real Time Visitor Stats plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.1.1 This is due to insufficient output escaping on the post author's nickname in the statcounter_addToTags() function. The function is hooked to wp_head and fires on every single post page. It retrieves the post author's nickname via the_author_meta() and echoes it directly into a JavaScript double-quoted string context inside a <script> block without applying esc_js() or any equivalent JavaScript-context escaping. This makes it possible for authenticated attackers with Author-level access and above to inject arbitrary web scripts into pages that will execute whenever any user (including unauthenticated visitors) accesses a post authored by the attacker. CVE record
- CVE-2025-13048, 19 Feb 2026
- The StatCounter - Free Real Time Visitor Stats plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the user's Nickname in all versions up to, and including, 2.1.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 record
- CVE-2021-24920, 28 Feb 2022
- The StatCounter WordPress plugin before 2.0.7 does not sanitise and escape the Project ID and Secure Code settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed CVE record
What to do if you run StatCounter
If you run StatCounter, 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 StatCounter vulnerabilities
Free. We email you when a new vulnerability is published for StatCounter, 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.