CVE-2026-6275 StatCounter <= 2.1.1 - Authenticated (Author+) Stored Cross-Site Scripting via Author Nickname
Authenticated attackers can inject arbitrary scripts via author nicknames, executing code on visitor pages in the StatCounter WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-6275?
CVE-2026-6275 is a medium-severity cross-site scripting vulnerability in StatCounter – Free Real Time Visitor Stats, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-6275?
How do I fix CVE-2026-6275?
No fix has been published for CVE-2026-6275 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-6275 being exploited?
There is no known exploitation of CVE-2026-6275 in the wild and no public exploit code.
Sources
Also known as GHSA-fm82-44w2-4gmf.