MEDIUMCVSS v3.1 4.3Vulnerability

CVE-2026-69131

## 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)` — which returns `True` for `obj=None`, and 2. the Django model-level `delete_file` / `delete_folder` / `delete_image` permission (enforced downstream by the admin delete machinery). It 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`. Because `FolderPe

Properties

Summary
django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions
Severity
medium
Nvd fetched at
2026-11-19T03:31:17.617109+00:00
Cvss score
4.3
Cvss severity
MEDIUM
Retrieved at
2026-11-19T03:32:39+00:00
Ghsa published
2026-11-18T21:20:42Z
Source url
https://github.com/advisories/GHSA-vf85-8ff2-3r9w
Ghsa updated
2026-11-18T21:20:43Z
Ghsa id
GHSA-vf85-8ff2-3r9w
Last source
GitHub Advisory Database
Score
4.3
Cvss version
3.1
Cve id
CVE-2026-69131
Cvss vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
First seen by Signal
2026-11-18T23:15:15+00:00
Name
CVE-2026-69131
Is ghsa only
false
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Published at
2026-11-18T21:18:01.040

Related Entities (5)

AFFECTS (1)

→[Software]pip/django-filer

VULNERABLE_TO (1)

←[Software]pip/django-filer

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-69131 (CVSS v3.1 4.3) — Ninja Signal Threat Intelligence | Ninja Signal