<?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>Thu, 08 Oct 2026 13:54:20 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-277350</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277350</link>
      <description>EUVD-2026-277350</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277350</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33162</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33162</link>
      <description>&lt;p&gt;Craft CMS is a content management system (CMS). From version 5.3.0 to before version 5.9.14, an authenticated control panel user with only accessCp can move entries across sections via POST /actions/entries/move-to-section, even when they do not have saveEntries:{sectionUid} permission for either source or destination section. This issue has been patched in version 5.9.14.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft CMS is a content management system (CMS). From version 5.3.0 to before version 5.9.14, an authenticated control panel user with only accessCp can move entries across sections via POST /actions/entries/move-to-section, even when they do not have saveEntries:{sectionUid} permission for either source or destination section. This issue has been patched in version 5.9.14.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33162</guid>
    </item>
    <item>
      <title>GHSA-f582-6gf6-gx4g — Craft CMS has an authorization bypass which allows any control panel user to move entries without permissions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f582-6gf6-gx4g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An authenticated control panel user with only accessCp can move entries across sections via POST `/actions/entries/move-to-section`, even when they do not have `saveEntries:{sectionUid}` permission for either source or destination section.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;#### Root-cause analysis&lt;/p&gt;
&lt;p&gt;1. actionMoveToSection accepts sectionId and entryIds, loads entries, and iterates:
`Craft::$app-&amp;gt;getEntries()-&amp;gt;moveEntryToSection($entry, $section)`.
  2. The endpoint does not enforce per-entry or per-section authorization checks.
  3. `moveEntryToSection()` also does not enforce current-user authorization.
  4. There is a permission check in `actionMoveToSectionModalData` for building UI options, but that check is not enforced in the actual endpoint.
  5. Therefore, a direct POST request can bypass UI filtering and perform unauthorized entry moves.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;* This is an authorization bypass permitting unauthorized content changes.
* Authenticated low-privileged control panel users can move entries they should not be able to manage, violating integrity and potentially disrupting routing/editorial controls.&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;### Summary&lt;/p&gt;
&lt;p&gt;An authenticated control panel user with only accessCp can move entries across sections via POST `/actions/entries/move-to-section`, even when they do not have `saveEntries:{sectionUid}` permission for either source or destination section.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;#### Root-cause analysis&lt;/p&gt;
&lt;p&gt;1. actionMoveToSection accepts sectionId and entryIds, loads entries, and iterates:
`Craft::$app-&amp;gt;getEntries()-&amp;gt;moveEntryToSection($entry, $section)`.
  2. The endpoint does not enforce per-entry or per-section authorization checks.
  3. `moveEntryToSection()` also does not enforce current-user authorization.
  4. There is a permission check in `actionMoveToSectionModalData` for building UI options, but that check is not enforced in the actual endpoint.
  5. Therefore, a direct POST request can bypass UI filtering and perform unauthorized entry moves.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;* This is an authorization bypass permitting unauthorized content changes.
* Authenticated low-privileged control panel users can move entries they should not be able to manage, violating integrity and potentially disrupting routing/editorial controls.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f582-6gf6-gx4g</guid>
    </item>
  </channel>
</rss>
