<?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://db.gcve.eu</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, 09 Nov 2026 05:32:35 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-120540</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-120540</link>
      <description>&lt;p&gt;The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.13.6. This is due to the way iubendaParser::parse_comments() re-processes HTML inside IUB-COOKIE-BLOCK markers through the bundled simple_html_dom parser after WordPress has already KSES-filtered the saved comment: simple_html_dom&amp;#39;s remove_noise() stores &amp;lt;code&amp;gt; bodies under a deterministic key (&amp;#39;___noise___ 1000&amp;#39;) and restore_noise() later substitutes any matching substring back into attribute values WITHOUT re-escaping, allowing a quote-breaking payload stashed in an allowed &amp;lt;code&amp;gt; element to be injected into an allowed &amp;lt;abbr title=&amp;#34;___noise___ 1000&amp;#34;&amp;gt; attribute at render time. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator approves the first (otherwise moderated) comment under WordPress&amp;#39;s default comment_previously_approved setting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.13.6. This is due to the way iubendaParser::parse_comments() re-processes HTML inside IUB-COOKIE-BLOCK markers through the bundled simple_html_dom parser after WordPress has already KSES-filtered the saved comment: simple_html_dom&amp;#39;s remove_noise() stores &amp;lt;code&amp;gt; bodies under a deterministic key (&amp;#39;___noise___ 1000&amp;#39;) and restore_noise() later substitutes any matching substring back into attribute values WITHOUT re-escaping, allowing a quote-breaking payload stashed in an allowed &amp;lt;code&amp;gt; element to be injected into an allowed &amp;lt;abbr title=&amp;#34;___noise___ 1000&amp;#34;&amp;gt; attribute at render time. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator approves the first (otherwise moderated) comment under WordPress&amp;#39;s default comment_previously_approved setting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-120540</guid>
    </item>
    <item>
      <title>GHSA-qp3p-7592-f8mv</title>
      <link>https://db.gcve.eu/vuln/ghsa-qp3p-7592-f8mv</link>
      <description>&lt;p&gt;The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.13.6. This is due to the way iubendaParser::parse_comments() re-processes HTML inside IUB-COOKIE-BLOCK markers through the bundled simple_html_dom parser after WordPress has already KSES-filtered the saved comment: simple_html_dom&amp;#39;s remove_noise() stores &amp;lt;code&amp;gt; bodies under a deterministic key (&amp;#39;___noise___ 1000&amp;#39;) and restore_noise() later substitutes any matching substring back into attribute values WITHOUT re-escaping, allowing a quote-breaking payload stashed in an allowed &amp;lt;code&amp;gt; element to be injected into an allowed &amp;lt;abbr title=&amp;#34;___noise___ 1000&amp;#34;&amp;gt; attribute at render time. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator approves the first (otherwise moderated) comment under WordPress&amp;#39;s default comment_previously_approved setting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.13.6. This is due to the way iubendaParser::parse_comments() re-processes HTML inside IUB-COOKIE-BLOCK markers through the bundled simple_html_dom parser after WordPress has already KSES-filtered the saved comment: simple_html_dom&amp;#39;s remove_noise() stores &amp;lt;code&amp;gt; bodies under a deterministic key (&amp;#39;___noise___ 1000&amp;#39;) and restore_noise() later substitutes any matching substring back into attribute values WITHOUT re-escaping, allowing a quote-breaking payload stashed in an allowed &amp;lt;code&amp;gt; element to be injected into an allowed &amp;lt;abbr title=&amp;#34;___noise___ 1000&amp;#34;&amp;gt; attribute at render time. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator approves the first (otherwise moderated) comment under WordPress&amp;#39;s default comment_previously_approved setting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qp3p-7592-f8mv</guid>
    </item>
  </channel>
</rss>
