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

Published Nov 18, 2026
·
Updated

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 #1605. Upgrade to the first release containing that commit (3.5.0 or later).

Details

The deletefilesorfolders admin action in filer/admin/folderadmin.py authorized deletion using only:

1. self.hasdeletepermission(request) — which returns True for obj=None, and 2. the Django model-level deletefile / deletefolder / deleteimage permission (enforced downstream by the admin delete machinery).

It never called checkfoldereditpermissions or checkfileseditpermissions. 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 canedit grant from FolderPermission.

Because FolderPermission has no dedicated candelete field, deletion is treated as an edit/management operation and is gated elsewhere on canedit. 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 deletefile / deletefolder / deleteimage 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 deletefile / deletefolder / deleteimage permission to staff who are meant to be read-only on specific folders via FolderPermission.

Credit

Reported through coordinated disclosure. Fixed in PR #1605.

Other sources

django-filer is a file and image management application for Django. Prior to 3.5.0, the deletefilesorfolders action in filer/admin/folderadmin.py checks global Django model-level deletion permission but omits checkfoldereditpermissions and checkfileseditpermissions when FILERENABLEPERMISSIONS is enabled. An authenticated staff user who has a global deletefile, deletefolder, or deleteimage permission but is limited to read-only access by FolderPermission can therefore delete files, folders, and descendants from the restricted folder. Deployments using the default disabled per-folder permission system are not affected, and the issue does not create a read-confidentiality impact. This issue is fixed in version 3.5.0.

— MITRE

Affected Software

2 affected componentsFixes available
pip/django-filer<=3.4.4
3.5.0
pip/django-filer<3.5.0
3.5.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/django-filer to a version that resolves this vulnerability.

    Fixed in 3.5.0
  2. Upgrade

    Upgrade django-filer to a version that resolves this vulnerability.

    Fixed in 3.5.0
  3. Compensating control

    Until upgrading, do not grant folder-scoped read-only staff the Django model-level delete_file, delete_folder, or delete_image permissions.

Event History

Nov 18, 2026
CVE Published
via MITRE·09:10 PM
Data Sourced
via MITRE·09:10 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:18 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:20 PM
Data Sourced
via GitHub·09:20 PM
DescriptionSeverityWeaknessAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203