Skip to content
Laskyr

Plugins · official-statcounter-plugin-for-wordpress · data as of 2026-11-04

Is StatCounter safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.2.0)

As of 2026-11-04. 3 issues are on record for older versions; version 2.1.2 or newer fixes all of them that state a fix.

Latest version
2.2.0
Last updated
2026-08-19
Active installs
70,000+
Known issues on record
3
Unpatched in latest
0
Tested up to WP
7.0.8

Real-time visitor stats, session replay and heatmaps for your WordPress site. See exactly how visitors use your site - and why they leave. — by StatCounter

What to do

  1. Update to the latest version (2.2.0). Anything older than 2.1.2 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get official-statcounter-plugin-for-wordpress --field=version shows what you run; wp plugin update official-statcounter-plugin-for-wordpress updates it.

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.5 CVE-2026-57629 · published 2026-06-26

Cross-site scripting (XSS) in StatCounter (2.1.1 and older)

Affected
2.1.1 and older
Fixed in
2.1.2
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Contributor Cross Site Scripting (XSS) in StatCounter <= 2.1.1 versions.

NVD CVE-2026-57629Patchstack advisory

medium 6.4 CVE-2026-6275 · published 2026-05-29

Stored cross-site scripting (XSS) in StatCounter (2.1.1 and older)

Affected
2.1.1 and older
Fixed in
2.1.2 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

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.

NVD CVE-2026-6275Wordfence advisoryCode change (fix)Plugin source

medium 6.4 CVE-2025-13048 · published 2026-02-19

Stored cross-site scripting (XSS) in StatCounter (2.1.0 and older)

Affected
2.1.0 and older
Fixed in
2.1.1 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

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.

NVD CVE-2025-13048Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
StatCounter vulnerability status badge
<a href="https://laskyr.com/plugins/official-statcounter-plugin-for-wordpress"><img src="https://laskyr.com/plugins/official-statcounter-plugin-for-wordpress/badge.svg" alt="StatCounter vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit