<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 08:23:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-6275 — StatCounter &lt;= 2.1.1 - Authenticated (Author+) Stored Cross-Site Scripting via Author Nickname</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-6275</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; StatCounter – Free Real Time Visitor Stats&lt;/p&gt;
&lt;p&gt;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&amp;#39;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&amp;#39;s nickname via the_author_meta() and echoes it directly into a JavaScript double-quoted string context inside a &amp;lt;script&amp;gt; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; StatCounter – Free Real Time Visitor Stats&lt;/p&gt;
&lt;p&gt;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&amp;#39;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&amp;#39;s nickname via the_author_meta() and echoes it directly into a JavaScript double-quoted string context inside a &amp;lt;script&amp;gt; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-6275</guid>
    </item>
  </channel>
</rss>
