<?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://vulnerability.circl.lu</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>Sat, 10 Oct 2026 20:48:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-96840 — Post Grid Gutenberg Blocks &lt;= 5.1.0 - Unauthenticated Stored Cross-Site Scripting via display_name User Field</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-96840</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpxpo Post Grid Gutenberg Blocks – PostX&lt;/p&gt;
&lt;p&gt;The Post Grid Gutenberg Blocks – PostX plugin for WordPress is vulnerable to Stored Cross-Site Scripting via display_name User Field in all versions up to, and including, 5.1.0 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. WordPress core&amp;#39;s pre_user_display_name filter encodes &amp;amp;, &amp;lt;, and &amp;gt; but leaves double-quotes intact (ENT_NOQUOTES), allowing a Subscriber-level user to store a double-quote in their display_name via /wp-admin/profile.php that subsequently breaks out of the alt=&amp;#34;&amp;#34; attribute at Archive_Title.php:144.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpxpo Post Grid Gutenberg Blocks – PostX&lt;/p&gt;
&lt;p&gt;The Post Grid Gutenberg Blocks – PostX plugin for WordPress is vulnerable to Stored Cross-Site Scripting via display_name User Field in all versions up to, and including, 5.1.0 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. WordPress core&amp;#39;s pre_user_display_name filter encodes &amp;amp;, &amp;lt;, and &amp;gt; but leaves double-quotes intact (ENT_NOQUOTES), allowing a Subscriber-level user to store a double-quote in their display_name via /wp-admin/profile.php that subsequently breaks out of the alt=&amp;#34;&amp;#34; attribute at Archive_Title.php:144.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-96840</guid>
    </item>
  </channel>
</rss>
