CWE-285 · CWE-639 · CWE-862
## Summary When django-filer's optional per-folder permission system is enabled (`FILER_ENABLE_PERMISSIONS=True`), the "Delete files and/or folders" admin action does **not** enforce per-folder edit permissions the way every other mutating action does. A staff user who is scoped **read-only** on a folder via `FolderPermission` (`can_edit = DENY`), but who holds the global Django model-level `delete_*` permission, can delete files and entire subfolders inside that folder — even though their move, rename, copy, and resize actions on the same folder are correctly denied. This is an integrity / edit-control gap (unauthorized deletion). It is **not** a read-confidentiality issue: filer files are world-downloadable by design, so no confidentiality claim is made. ## Affected versions - django-filer `<= 3.4.4` (verified end-to-end on 3.4.4 and on `master` prior to the fix). Only installations running with `FILER_ENABLE_PERMISSIONS = True` (the optional per-folder `FolderPermission` system) are affected. Deployments that leave permissions disabled (the default) rely solely on Django model-level permissions and are not impacted by this specific gap. ## Patched versions - Fixed in PR [#1605](https://github.com/django-cms/django-filer/pull/1605). Upgrade to the first release containing that commit (`3.5.0` or later). ## Details The `delete_files_or_folders` admin action in `filer/admin/folderadmin.py` authorized deletion using only: 1. `self.has_delete_permission(request)