<?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 15:18:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-351210</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-351210</link>
      <description>EUVD-2026-351210</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-351210</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72785</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72785</link>
      <description>&lt;p&gt;Craft CMS 5.0.0-RC1 through 5.10.5 contains an incorrect authorization vulnerability. A control-panel user holding only the viewCategories permission (without saveCategories) for a category group can permanently modify that group&amp;#39;s category structure — reordering and re-parenting categories — via the structures/move-element action. The structureEditable flag is computed from the view permission rather than the save permission, and the StructuresController authorizes the mutating action on that read-time session grant without a save re-check. Because a category&amp;#39;s URI is derived from its position in the structure, moving a category changes its URL and those of its descendants and can corrupt navigation menus built from the category taxonomy. The issue is fixed in 5.10.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft CMS 5.0.0-RC1 through 5.10.5 contains an incorrect authorization vulnerability. A control-panel user holding only the viewCategories permission (without saveCategories) for a category group can permanently modify that group&amp;#39;s category structure — reordering and re-parenting categories — via the structures/move-element action. The structureEditable flag is computed from the view permission rather than the save permission, and the StructuresController authorizes the mutating action on that read-time session grant without a save re-check. Because a category&amp;#39;s URI is derived from its position in the structure, moving a category changes its URL and those of its descendants and can corrupt navigation menus built from the category taxonomy. The issue is fixed in 5.10.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72785</guid>
    </item>
    <item>
      <title>GHSA-xxpx-f366-4xpq — Craft CMS: Authorization bypass: view-only Categories user can modify category structure via structures/move-element</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xxpx-f366-4xpq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;A control-panel user who holds only the viewCategories permission for a category group (and not saveCategories) can permanently modify that group&amp;#39;s category structure — reordering and re-parenting categories via the structures/move-element action.&lt;/p&gt;
&lt;p&gt;A read-time authorization grant that a write endpoint later trusts. For categories, the structureEditable flag is computed from the view permission (`src/elements/Category.php:205`) instead of the save permission (entries correctly use saveEntries — `src/elements/Entry.php:341`). When the read-only category index renders, `craft\base\Element::indexHtml()` calls `Craft::$app-&amp;gt;getSession()-&amp;gt;authorize(&amp;#39;editStructure:&amp;lt;structureId&amp;gt;&amp;#39;);` StructuresController then authorizes the structure-mutating action solely on that session grant, with no canSave re-check.&lt;/p&gt;
&lt;p&gt;Verified on Craft CMS 5.10.5. Same class as the moderate-severity authorization bypasses fixed in 5.10.3 and 5.10.5; this is a distinct, unpatched instance.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A low-privileged, authenticated user (view-only on a category group) can persistently alter the sibling ordering and parent/child nesting of the category taxonomy. Because a category’s URI is derived from its position in the structure (ancestor slugs), moving a category changes its URL and the URLs of its descendants, and can corrupt any navigation/menus built from the category tree. This is an integrity/broken access-control issue: content that the user has no permission to modify is being modified. No confidentiali…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;A control-panel user who holds only the viewCategories permission for a category group (and not saveCategories) can permanently modify that group&amp;#39;s category structure — reordering and re-parenting categories via the structures/move-element action.&lt;/p&gt;
&lt;p&gt;A read-time authorization grant that a write endpoint later trusts. For categories, the structureEditable flag is computed from the view permission (`src/elements/Category.php:205`) instead of the save permission (entries correctly use saveEntries — `src/elements/Entry.php:341`). When the read-only category index renders, `craft\base\Element::indexHtml()` calls `Craft::$app-&amp;gt;getSession()-&amp;gt;authorize(&amp;#39;editStructure:&amp;lt;structureId&amp;gt;&amp;#39;);` StructuresController then authorizes the structure-mutating action solely on that session grant, with no canSave re-check.&lt;/p&gt;
&lt;p&gt;Verified on Craft CMS 5.10.5. Same class as the moderate-severity authorization bypasses fixed in 5.10.3 and 5.10.5; this is a distinct, unpatched instance.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;A low-privileged, authenticated user (view-only on a category group) can persistently alter the sibling ordering and parent/child nesting of the category taxonomy. Because a category’s URI is derived from its position in the structure (ancestor slugs), moving a category changes its URL and the URLs of its descendants, and can corrupt any navigation/menus built from the category tree. This is an integrity/broken access-control issue: content that the user has no permission to modify is being modified. No confidentiali…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xxpx-f366-4xpq</guid>
    </item>
  </channel>
</rss>
