<?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>Mon, 12 Oct 2026 13:47:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-8977 — WP GDPR Cookie Consent &lt;= 1.0.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'ninja_gdpr_ajax_actions'…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-8977</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; techjewel WP GDPR Cookie Consent&lt;/p&gt;
&lt;p&gt;The WP GDPR Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;ninja_gdpr_ajax_actions&amp;#39; AJAX action in versions up to, and including, 1.0.0. This is due to missing capability and nonce checks on the handleAjaxCalls() function, combined with insufficient input sanitization on the gdprConfig values and missing output escaping in the generateCSS() function which echoes stored configuration values directly into a &amp;lt;style&amp;gt; block rendered on wp_head. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; techjewel WP GDPR Cookie Consent&lt;/p&gt;
&lt;p&gt;The WP GDPR Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;ninja_gdpr_ajax_actions&amp;#39; AJAX action in versions up to, and including, 1.0.0. This is due to missing capability and nonce checks on the handleAjaxCalls() function, combined with insufficient input sanitization on the gdprConfig values and missing output escaping in the generateCSS() function which echoes stored configuration values directly into a &amp;lt;style&amp;gt; block rendered on wp_head. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-8977</guid>
    </item>
  </channel>
</rss>
