<?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 04:28:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-28781 — Craft Affected by Entries Authorship Spoofing via Mass Assignment</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-28781</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; craftcms cms&lt;/p&gt;
&lt;p&gt;Craft is a content management system (CMS). Prior to 4.17.0-beta.1 and 5.9.0-beta.1, the entry creation process allows for Mass Assignment of the authorId attribute. A user with &amp;#34;Create Entries&amp;#34; permission can inject the authorIds[] (or authorId) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others. Normally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively &amp;#34;spoofs&amp;#34; the authorship. This vulnerability is fixed in 4.17.0-beta.1 and 5.9.0-beta.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; craftcms cms&lt;/p&gt;
&lt;p&gt;Craft is a content management system (CMS). Prior to 4.17.0-beta.1 and 5.9.0-beta.1, the entry creation process allows for Mass Assignment of the authorId attribute. A user with &amp;#34;Create Entries&amp;#34; permission can inject the authorIds[] (or authorId) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others. Normally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively &amp;#34;spoofs&amp;#34; the authorship. This vulnerability is fixed in 4.17.0-beta.1 and 5.9.0-beta.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-28781</guid>
    </item>
  </channel>
</rss>
