<?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>Sat, 17 Oct 2026 19:35:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-332254</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-332254</link>
      <description>EUVD-2026-332254</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-332254</guid>
    </item>
    <item>
      <title>fkie_cve-2026-50284</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-50284</link>
      <description>&lt;p&gt;Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.21 and 4.0.0-RC1 through 4.17.14, theAssetsController::actionDeleteFolder() only requires the deleteAssets:&amp;lt;volume-uid&amp;gt; permission for the target folder. It never enforces deletePeerAssets:&amp;lt;volume-uid&amp;gt;, even though Assets::deleteFoldersByIds() cascades deletion to every descendant folder and every asset inside, regardless of the uploader&amp;#39;s assigned privileges. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling actionDeleteAsset endpoint correctly applies. This issue has been fixed in versions 4.17.15 and 5.9.22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.21 and 4.0.0-RC1 through 4.17.14, theAssetsController::actionDeleteFolder() only requires the deleteAssets:&amp;lt;volume-uid&amp;gt; permission for the target folder. It never enforces deletePeerAssets:&amp;lt;volume-uid&amp;gt;, even though Assets::deleteFoldersByIds() cascades deletion to every descendant folder and every asset inside, regardless of the uploader&amp;#39;s assigned privileges. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling actionDeleteAsset endpoint correctly applies. This issue has been fixed in versions 4.17.15 and 5.9.22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-50284</guid>
    </item>
    <item>
      <title>GHSA-7h62-6v23-v8fm — Craft CMS: Missing peer-permission check in `AssetsController::actionDeleteFolder` allows deletion of other users' asse…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7h62-6v23-v8fm</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;`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:&amp;lt;volume-uid&amp;gt;` permission for the target folder. It never enforces `deletePeerAssets:&amp;lt;volume-uid&amp;gt;`, even though `Assets::deleteFoldersByIds()` cascades deletion to every descendant folder and every asset inside, regardless of who uploaded them. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling `actionDeleteAsset` endpoint correctly applies.&lt;/p&gt;
&lt;p&gt;This is the same bug class that was just fixed in `actionMoveFolder` as **GHSA-3w32-23wj-rxg3** (commit `05c2042`, Apr 23 2026); the fix added `requireVolumePermissionByFolder(&amp;#39;deletePeerAssets&amp;#39;, …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`src/controllers/AssetsController.php:552-569`:&lt;/p&gt;
&lt;p&gt;```php
public function actionDeleteFolder(): Response
{
    $this-&amp;gt;requireAcceptsJson();
    $folderId = $this-&amp;gt;request-&amp;gt;getRequiredBodyParam(&amp;#39;folderId&amp;#39;);&lt;/p&gt;
&lt;p&gt;$assets = Craft::$app-&amp;gt;getAssets();
    $folder = $assets-&amp;gt;getFolderById($folderId);&lt;/p&gt;
&lt;p&gt;if (!$folder) {
        throw new BadRequestHttpException(&amp;#39;The folder cannot be found&amp;#39;);
    }&lt;/p&gt;
&lt;p&gt;// Check if it&amp;#39;s possible to delete objects in the target volume.
    $this-&amp;gt;requireVolumePermissionByFolder(&amp;#39;deleteAssets&amp;#39;, $folder); // &amp;lt;-- only checks deleteAssets
    $assets-&amp;gt;deleteFold…&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;`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:&amp;lt;volume-uid&amp;gt;` permission for the target folder. It never enforces `deletePeerAssets:&amp;lt;volume-uid&amp;gt;`, even though `Assets::deleteFoldersByIds()` cascades deletion to every descendant folder and every asset inside, regardless of who uploaded them. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling `actionDeleteAsset` endpoint correctly applies.&lt;/p&gt;
&lt;p&gt;This is the same bug class that was just fixed in `actionMoveFolder` as **GHSA-3w32-23wj-rxg3** (commit `05c2042`, Apr 23 2026); the fix added `requireVolumePermissionByFolder(&amp;#39;deletePeerAssets&amp;#39;, …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`src/controllers/AssetsController.php:552-569`:&lt;/p&gt;
&lt;p&gt;```php
public function actionDeleteFolder(): Response
{
    $this-&amp;gt;requireAcceptsJson();
    $folderId = $this-&amp;gt;request-&amp;gt;getRequiredBodyParam(&amp;#39;folderId&amp;#39;);&lt;/p&gt;
&lt;p&gt;$assets = Craft::$app-&amp;gt;getAssets();
    $folder = $assets-&amp;gt;getFolderById($folderId);&lt;/p&gt;
&lt;p&gt;if (!$folder) {
        throw new BadRequestHttpException(&amp;#39;The folder cannot be found&amp;#39;);
    }&lt;/p&gt;
&lt;p&gt;// Check if it&amp;#39;s possible to delete objects in the target volume.
    $this-&amp;gt;requireVolumePermissionByFolder(&amp;#39;deleteAssets&amp;#39;, $folder); // &amp;lt;-- only checks deleteAssets
    $assets-&amp;gt;deleteFold…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7h62-6v23-v8fm</guid>
    </item>
  </channel>
</rss>
