CVE-2026-6275: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statcounter StatCounter – Free Real Time Visitor Stats
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.
AI Analysis
Technical Summary
CVE-2026-6275 is a stored cross-site scripting vulnerability in the StatCounter – Free Real Time Visitor Stats WordPress plugin (up to version 2.1.1). The issue arises from insufficient output escaping of the post author's nickname in the statcounter_addToTags() function, which is hooked to wp_head and runs on every post page. The function retrieves the author's nickname via the_author_meta() and injects it directly into a JavaScript double-quoted string inside a <script> block without applying esc_js() or equivalent escaping. This allows authenticated users with Author-level privileges or higher to inject arbitrary JavaScript that executes in the context of any visitor viewing the post.
Potential Impact
An attacker with Author-level access or higher can inject malicious JavaScript code into posts, which will execute in the browsers of any users viewing those posts, including unauthenticated visitors. This can lead to theft of session cookies, defacement, or other client-side attacks. The vulnerability does not affect availability but impacts confidentiality and integrity. The CVSS 3.1 base score is 6.4 (medium severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and partial confidentiality and integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Author-level access to trusted users only. Consider applying manual code fixes to properly escape the author's nickname in the JavaScript context using esc_js() or equivalent. Monitor official StatCounter and WordPress plugin repositories for updates addressing this vulnerability.
CVE-2026-6275: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in statcounter StatCounter – Free Real Time Visitor Stats
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.
CVSS v3.1
Score 6.4medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-6275 is a stored cross-site scripting vulnerability in the StatCounter – Free Real Time Visitor Stats WordPress plugin (up to version 2.1.1). The issue arises from insufficient output escaping of the post author's nickname in the statcounter_addToTags() function, which is hooked to wp_head and runs on every post page. The function retrieves the author's nickname via the_author_meta() and injects it directly into a JavaScript double-quoted string inside a <script> block without applying esc_js() or equivalent escaping. This allows authenticated users with Author-level privileges or higher to inject arbitrary JavaScript that executes in the context of any visitor viewing the post.
Potential Impact
An attacker with Author-level access or higher can inject malicious JavaScript code into posts, which will execute in the browsers of any users viewing those posts, including unauthenticated visitors. This can lead to theft of session cookies, defacement, or other client-side attacks. The vulnerability does not affect availability but impacts confidentiality and integrity. The CVSS 3.1 base score is 6.4 (medium severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and partial confidentiality and integrity impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Author-level access to trusted users only. Consider applying manual code fixes to properly escape the author's nickname in the JavaScript context using esc_js() or equivalent. Monitor official StatCounter and WordPress plugin repositories for updates addressing this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-04-14T13:44:26.816Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a19333de29bf47b509b31ad
Added to database: 5/29/2026, 6:33:33 AM
Last enriched: 5/29/2026, 6:49:02 AM
Last updated: 5/29/2026, 6:13:31 PM
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.