CVE Feed
4.3 Medium

django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions

CVE-2026-69131

Summary When django-filer's optional per-folder permission system is enabled (FILERENABLEPERMISSIONS=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 (canedit = 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 FILERENABLEPERMISSIONS = 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…

Assessment

CVSS
4.3 (v3.1)
Severity
Medium
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
18 November 2026
Last updated
18 November 2026
Affected
django-filer
Weakness
CWE-285, CWE-639, CWE-862

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-69131