<?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, 02 Nov 2026 22:29:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-111254 — W3 Total Cache &lt;= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-111254</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; boldgrid W3 Total Cache&lt;/p&gt;
&lt;p&gt;The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;comment&amp;#39; parameter in all versions up to, and including, 2.10.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that a Pro license was previously active with REST caching enabled and has since become inactive while Disk Enhanced page caching remains configured, and that the attacker holds a previously approved commenter identity.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; boldgrid W3 Total Cache&lt;/p&gt;
&lt;p&gt;The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;comment&amp;#39; parameter in all versions up to, and including, 2.10.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that a Pro license was previously active with REST caching enabled and has since become inactive while Disk Enhanced page caching remains configured, and that the attacker holds a previously approved commenter identity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-111254</guid>
    </item>
  </channel>
</rss>
