CVE-2026-69131: django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions
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.
References
- github.com/advisories/GHSA-vf85-8ff2-3r9w
- github.com/django-cms/django-filer/commit/29d20ec0de13d7f77fa2cea93166f8d50a3f508d
- github.com/django-cms/django-filer/commit/742ba4c3094dd75e586ca3a05e6ad2703de4553b
- github.com/django-cms/django-filer/pull/1605
- github.com/django-cms/django-filer/releases/tag/3.5.0
- github.com/django-cms/django-filer/security/advisories/GHSA-vf85-8ff2-3r9w
- nvd.nist.gov/vuln/detail/CVE-2026-69131
Code Behaviors & Features
Detect and mitigate CVE-2026-69131 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →