{"items":[{"id":"NVI-00006462","kind":"vulnerability","title":"Craft CMS: Missing peer-permission check in `AssetsController::actionDeleteFolder` allows deletion of other users' assets","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7h62-6v23-v8fm","CVE-2026-50284"],"plain_summary":"GitHub lists this reviewed advisory for craftcms/cms, craftcms/cms. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1baea2a0f748b62d23df618770825694"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.9.22 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.15 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-25T21:10:00.770Z","value":"7.1 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-8e45a6305e81146d1797da22b9d1a77e"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.387%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32769. Missing scores are unknown.","source_id":"sr-1baea2a0f748b62d23df618770825694"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0e3750d4985d01e3ff6210ac1661c31b","url":"https://github.com/advisories/GHSA-7h62-6v23-v8fm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-7h62-6v23-v8fm","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T03:47:42.887Z"},{"id":"sr-b5ae4866d94a30f46688944b484e56e2","url":"https://github.com/advisories/GHSA-7h62-6v23-v8fm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7h62-6v23-v8fm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.950Z"},{"id":"sr-8e45a6305e81146d1797da22b9d1a77e","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-50284","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-50284","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-1baea2a0f748b62d23df618770825694","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-50284","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0e3750d4985d01e3ff6210ac1661c31b"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":[">= 5.0.0-RC1, < 5.9.22"]},{"certainty":"source_listed","source_ids":["sr-0e3750d4985d01e3ff6210ac1661c31b"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":[">= 4.0.0-RC1, < 4.17.15"]},{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.22"]},{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.15"]}],"null_published_at":"2026-11-05T19:10:21.400Z","source_updated_at":"2026-07-02T18:49:08.000Z","source_disclosed_at":"2026-07-02T18:49:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:59.950Z"},{"id":"NVI-00006462","kind":"vulnerability","title":"Craft CMS: Missing peer-permission check in `AssetsController::actionDeleteFolder` allows deletion of other users' assets","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-7h62-6v23-v8fm","CVE-2026-50284"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.22 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.15 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1baea2a0f748b62d23df618770825694"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-25T21:10:00.770Z","value":"7.1 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-8e45a6305e81146d1797da22b9d1a77e"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.387%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32769. Missing scores are unknown.","source_id":"sr-1baea2a0f748b62d23df618770825694"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b5ae4866d94a30f46688944b484e56e2","url":"https://github.com/advisories/GHSA-7h62-6v23-v8fm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7h62-6v23-v8fm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.950Z"},{"id":"sr-8e45a6305e81146d1797da22b9d1a77e","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-50284","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-50284","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-1baea2a0f748b62d23df618770825694","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-50284","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.22"]},{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.15"]}],"null_published_at":"2026-11-03T17:49:21.371Z","source_updated_at":"2026-09-10T03:50:51.598Z","source_disclosed_at":"2026-07-02T18:49:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:59.950Z"},{"id":"NVI-00006462","kind":"vulnerability","title":"Craft CMS: Missing peer-permission check in `AssetsController::actionDeleteFolder` allows deletion of other users' assets","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-7h62-6v23-v8fm","CVE-2026-50284"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.22 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.15 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1baea2a0f748b62d23df618770825694"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.387%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32769. Missing scores are unknown.","source_id":"sr-1baea2a0f748b62d23df618770825694"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b5ae4866d94a30f46688944b484e56e2","url":"https://github.com/advisories/GHSA-7h62-6v23-v8fm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7h62-6v23-v8fm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.950Z"},{"id":"sr-1baea2a0f748b62d23df618770825694","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-50284","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.22"]},{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.15"]}],"null_published_at":"2026-10-31T22:27:09.603Z","source_updated_at":"2026-09-10T03:50:51.598Z","source_disclosed_at":"2026-07-02T18:49:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.950Z"},{"id":"NVI-00006462","kind":"vulnerability","title":"Craft CMS: Missing peer-permission check in `AssetsController::actionDeleteFolder` allows deletion of other users' assets","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-7h62-6v23-v8fm","CVE-2026-50284"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.22 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.15 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b5ae4866d94a30f46688944b484e56e2","url":"https://github.com/advisories/GHSA-7h62-6v23-v8fm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-7h62-6v23-v8fm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.950Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.22"]},{"certainty":"source_listed","source_ids":["sr-b5ae4866d94a30f46688944b484e56e2"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Summary\n\n`AssetsController::actionDeleteFolder()` only requires the `deleteAssets:` permission for the target folder. It never enforces `deletePeerAssets:`, 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.\n\nThis 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('deletePeerAssets', …)` and `savePeerAssets` checks to the move endpoint but did not propagate to the delete-folder endpoint.\n\n## Details\n\n`src/controllers/AssetsController.php:552-569`:\n\n```php\npublic function actionDeleteFolder(): Response\n{\n    $this->requireAcceptsJson();\n    $folderId = $this->request->getRequiredBodyParam('folderId');\n\n    $assets = Craft::$app->getAssets();\n    $folder = $assets->getFolderById($folderI","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.15"]}],"null_published_at":"2026-10-31T22:13:10.057Z","source_updated_at":"2026-09-10T03:50:51.598Z","source_disclosed_at":"2026-07-02T18:49:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:59.950Z"}],"next_cursor":null,"snapshot_revision":"42594"}