<?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>Mon, 28 Sep 2026 20:49:12 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-92589</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-92589</link>
      <description>&lt;p&gt;Craft CMS 5.0.0 through 5.10.12 (fixed in 5.10.13) contains a broken access control flaw in the nested-elements reorder endpoint. When an authenticated control panel user with viewEntries and viewPeerEntries (but without savePeerEntries) opens another author&amp;#39;s entry in read-only mode, Craft unconditionally grants that session a `manageNestedElements::&amp;lt;ownerId&amp;gt;::field:&amp;lt;handle&amp;gt;` authorization flag for the entry&amp;#39;s Matrix/Address fields. Unlike the corresponding delete endpoint, actions/nested-elements/reorder trusts this session flag alone and never rechecks the caller&amp;#39;s save permission for the owner element. As a result, a view-only user can POST to actions/nested-elements/reorder using the ownerElementType, ownerId, ownerSiteId, attribute, elementIds, and offset parameters present in the read-only page source and rewrite the sort order of Matrix blocks or Addresses belonging to content they are explicitly denied save access to.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft CMS 5.0.0 through 5.10.12 (fixed in 5.10.13) contains a broken access control flaw in the nested-elements reorder endpoint. When an authenticated control panel user with viewEntries and viewPeerEntries (but without savePeerEntries) opens another author&amp;#39;s entry in read-only mode, Craft unconditionally grants that session a `manageNestedElements::&amp;lt;ownerId&amp;gt;::field:&amp;lt;handle&amp;gt;` authorization flag for the entry&amp;#39;s Matrix/Address fields. Unlike the corresponding delete endpoint, actions/nested-elements/reorder trusts this session flag alone and never rechecks the caller&amp;#39;s save permission for the owner element. As a result, a view-only user can POST to actions/nested-elements/reorder using the ownerElementType, ownerId, ownerSiteId, attribute, elementIds, and offset parameters present in the read-only page source and rewrite the sort order of Matrix blocks or Addresses belonging to content they are explicitly denied save access to.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-92589</guid>
    </item>
    <item>
      <title>GHSA-mhr8-6rjx-8fjw</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mhr8-6rjx-8fjw</link>
      <description>&lt;p&gt;Craft CMS 5.0.0 through 5.10.12 (fixed in 5.10.13) contains a broken access control flaw in the nested-elements reorder endpoint. When an authenticated control panel user with viewEntries and viewPeerEntries (but without savePeerEntries) opens another author&amp;#39;s entry in read-only mode, Craft unconditionally grants that session a `manageNestedElements::&amp;lt;ownerId&amp;gt;::field:&amp;lt;handle&amp;gt;` authorization flag for the entry&amp;#39;s Matrix/Address fields. Unlike the corresponding delete endpoint, actions/nested-elements/reorder trusts this session flag alone and never rechecks the caller&amp;#39;s save permission for the owner element. As a result, a view-only user can POST to actions/nested-elements/reorder using the ownerElementType, ownerId, ownerSiteId, attribute, elementIds, and offset parameters present in the read-only page source and rewrite the sort order of Matrix blocks or Addresses belonging to content they are explicitly denied save access to.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft CMS 5.0.0 through 5.10.12 (fixed in 5.10.13) contains a broken access control flaw in the nested-elements reorder endpoint. When an authenticated control panel user with viewEntries and viewPeerEntries (but without savePeerEntries) opens another author&amp;#39;s entry in read-only mode, Craft unconditionally grants that session a `manageNestedElements::&amp;lt;ownerId&amp;gt;::field:&amp;lt;handle&amp;gt;` authorization flag for the entry&amp;#39;s Matrix/Address fields. Unlike the corresponding delete endpoint, actions/nested-elements/reorder trusts this session flag alone and never rechecks the caller&amp;#39;s save permission for the owner element. As a result, a view-only user can POST to actions/nested-elements/reorder using the ownerElementType, ownerId, ownerSiteId, attribute, elementIds, and offset parameters present in the read-only page source and rewrite the sort order of Matrix blocks or Addresses belonging to content they are explicitly denied save access to.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mhr8-6rjx-8fjw</guid>
    </item>
  </channel>
</rss>
