Vulnerabilities and security researches forofficial-statcounter-plugin-for-wordpress official-statcounter-plugin-for-wordpress

Jun 06, 2024

CVE, Research URL: CVE-2021-24920
Home page URL: Security reports for StatCounter – Free Real Time Visitor Stats
Application: StatCounter – Free Real Time Visitor Stats
Date: Feb 28, 2022
Research Description: 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
Affected versions: max 2.0.7.
Status: vulnerable

Mar 29, 2026

CVE, Research URL: CVE-2025-13048
Home page URL: Security reports for StatCounter – Free Real Time Visitor Stats
Application: StatCounter – Free Real Time Visitor Stats
Date: Feb 19, 2026
Research Description: 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.
Affected versions: max 2.1.1.
Status: vulnerable

May 31, 2026

CVE, Research URL: CVE-2026-6275
Home page URL: Security reports for StatCounter – Free Real Time Visitor Stats
Application: StatCounter – Free Real Time Visitor Stats
Date: May 29, 2026
Research Description: 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.
Affected versions: max 2.1.2.
Status: vulnerable