<?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>Fri, 09 Oct 2026 01:07:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-9019 — Easy Image Collage &lt;= 1.13.6 - Authenticated (Author+) Stored Cross-Site Scripting via 'grid[properties][borderColor]'…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-9019</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; brechtvds Easy Image Collage&lt;/p&gt;
&lt;p&gt;The Easy Image Collage plugin for WordPress is vulnerable to Stored Cross-Site Scripting via &amp;#39;grid[properties][borderColor]&amp;#39; and &amp;#39;grid[images][N][attachment_url]&amp;#39; Parameters in all versions up to, and including, 1.13.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the data is stored via update_post_meta() rather than wp_insert_post() post content, WordPress&amp;#39;s unfiltered_html restriction does not apply, meaning Authors cannot be blocked from this attack path by capability controls alone.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; brechtvds Easy Image Collage&lt;/p&gt;
&lt;p&gt;The Easy Image Collage plugin for WordPress is vulnerable to Stored Cross-Site Scripting via &amp;#39;grid[properties][borderColor]&amp;#39; and &amp;#39;grid[images][N][attachment_url]&amp;#39; Parameters in all versions up to, and including, 1.13.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the data is stored via update_post_meta() rather than wp_insert_post() post content, WordPress&amp;#39;s unfiltered_html restriction does not apply, meaning Authors cannot be blocked from this attack path by capability controls alone.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-9019</guid>
    </item>
  </channel>
</rss>
