1 line
5.3 KiB
JSON
1 line
5.3 KiB
JSON
{"schema_version":"1.9.2","id":"GHSA-vf85-8ff2-3r9w","published":"2026-11-18T21:20:42Z","modified":"2026-11-18T21:30:14.031723989Z","aliases":["CVE-2026-69131"],"summary":"django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions","details":"## Summary\n\nWhen 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.\n\nThis 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.\n\n## Affected versions\n\n- django-filer `<= 3.4.4` (verified end-to-end on 3.4.4 and on `master` prior to the fix).\n\nOnly 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.\n\n## Patched versions\n\n- 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).\n\n## Details\n\nThe `delete_files_or_folders` admin action in `filer/admin/folderadmin.py` authorized deletion using only:\n\n1. `self.has_delete_permission(request)` — which returns `True` for `obj=None`, and\n2. the Django model-level `delete_file` / `delete_folder` / `delete_image` permission (enforced downstream by the admin delete machinery).\n\nIt never called `check_folder_edit_permissions` or `check_files_edit_permissions`. Every sibling mutating action — move, rename, copy, resize — *does* call these helpers, which walk the selected objects (and their descendants) and enforce the per-folder `can_edit` grant from `FolderPermission`.\n\nBecause `FolderPermission` has no dedicated `can_delete` field, deletion is treated as an edit/management operation and is gated elsewhere on `can_edit`. The delete action's omission therefore let a folder-scoped read-only user bypass the per-folder control that constrains all their other write operations.\n\n### Precondition \n\nThe attacker must hold the Django model-level `delete_file` / `delete_folder` / `delete_image` permission. A purely read-only user (no model-level delete perm) receives `403` and cannot exploit this. This precondition matches the standard folder-scoped-staff deployment model, where staff hold model-level permissions and are further constrained per-folder by `FolderPermission`. \n\n## Mitigation\n\n- Upgrade to the patched release.\n- Until upgrading, avoid granting the model-level `delete_file` /\n `delete_folder` / `delete_image` permission to staff who are meant to be\n read-only on specific folders via `FolderPermission`.\n\n## Credit\n\nReported through coordinated disclosure. Fixed in PR #1605.","affected":[{"package":{"name":"django-filer","ecosystem":"PyPI","purl":"pkg:pypi/django-filer"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.0"}]}],"versions":["0.1.3a","0.7.0","0.7.1","0.7.2","0.8.1","0.8.2","0.8.3","0.8.4","0.8.5","0.8.6","0.8.7","0.9","0.9.1","0.9.10","0.9.11","0.9.12","0.9.2","0.9.3","0.9.4","0.9.5","0.9.6","0.9.7","0.9.8","0.9.9","1.0.0","1.0.1","1.0.2","1.0.3","1.0.4","1.0.5","1.0.6","1.1.0","1.1.1","1.2.0","1.2.1","1.2.2","1.2.3","1.2.4","1.2.5","1.2.6","1.2.6rc1","1.2.6rc2","1.2.7","1.2.8","1.3.0","1.3.1","1.3.2","1.4.0","1.4.1","1.4.2","1.4.3","1.4.4","1.5.0","1.6.0","1.7.0","1.7.1","2.0.0","2.0.1","2.0.2","2.1","2.1.1","2.1.2","2.1rc1","2.1rc2","2.1rc3","2.1rc4","2.2","2.2.1","2.2.2","2.2.3","2.2.4","2.2.5","2.2.6","2.2.7","2.2.8","2.3rc1","3.0.0","3.0.0rc1","3.0.0rc2","3.0.0rc3","3.0.1","3.0.2","3.0.3","3.0.4","3.0.5","3.0.6","3.1.0","3.1.1","3.1.2","3.1.3","3.1.4","3.2.0","3.2.1","3.2.2","3.2.3","3.3.0","3.3.1","3.3.2","3.3.3","3.4.0","3.4.1","3.4.2","3.4.3","3.4.4"],"database_specific":{"last_known_affected_version_range":"<= 3.4.4","source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-vf85-8ff2-3r9w/GHSA-vf85-8ff2-3r9w.json"}}],"references":[{"type":"WEB","url":"https://github.com/django-cms/django-filer/security/advisories/GHSA-vf85-8ff2-3r9w"},{"type":"WEB","url":"https://github.com/django-cms/django-filer/pull/1605"},{"type":"WEB","url":"https://github.com/django-cms/django-filer/commit/29d20ec0de13d7f77fa2cea93166f8d50a3f508d"},{"type":"WEB","url":"https://github.com/django-cms/django-filer/commit/742ba4c3094dd75e586ca3a05e6ad2703de4553b"},{"type":"PACKAGE","url":"https://github.com/django-cms/django-filer"},{"type":"WEB","url":"https://github.com/django-cms/django-filer/releases/tag/3.5.0"}],"database_specific":{"cwe_ids":["CWE-285","CWE-639","CWE-862"],"github_reviewed":true,"github_reviewed_at":"2026-11-18T21:20:42Z","nvd_published_at":null,"severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"}]} |