Medium

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

  • Disclosed: 18.11.2026
  • Updated: 18.11.2026 23:17

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. 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 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.

Precondition

The 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.

Mitigation

  • Upgrade to the patched release.
  • Until upgrading, avoid granting the model-level delete_file / delete_folder / delete_image permission to staff who are meant to be read-only on specific folders via FolderPermission.

Credit

Reported through coordinated disclosure. Fixed in PR #1605.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) django-filer < 3.5.0 3.5.0

References

CVSS score 4.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness (CWE)
CWE-285, CWE-639, CWE-862
Platform
Python (PyPI)
Package
django-filer
Disclosed
18.11.2026
Updated
18.11.2026 23:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-vf85-8ff2-3r9w - CC BY 4.0

Vulnerability history: django-filer

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
2
First → latest
11.2024 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Medium 2

Disclosures per year

  1. 2024: 1
  2. 2025: 0
  3. 2026: 1
  1. django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions this entry
    Medium · 4.3 CVE-2026-69131 < 3.5.0 3.5.0
  2. Medium · 5.5 CVE-2024-11404 < 3.3.0 3.3.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.