GHSA-vf85-8ff2-3r9w

Suggest an improvement
Source
https://github.com/advisories/GHSA-vf85-8ff2-3r9w
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-vf85-8ff2-3r9w/GHSA-vf85-8ff2-3r9w.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-vf85-8ff2-3r9w
Aliases
  • CVE-2026-69131
Published
2026-11-18T21:20:42Z
Modified
2026-11-18T21:30:14Z
Severity
  • 4.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N CVSS Calculator
Summary
django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions
Details

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.

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"
}
References

Affected packages

PyPI / django-filer

Package

Name
django-filer
View open source insights on deps.dev
Purl
pkg:pypi/django-filer

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
3.5.0

Affected versions

0.*
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.2
0.9.3
0.9.4
0.9.5
0.9.6
0.9.7
0.9.8
0.9.9
0.9.10
0.9.11
0.9.12
1.*
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.6rc1
1.2.6rc2
1.2.6
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.*
2.0.0
2.0.1
2.0.2
2.1rc1
2.1rc2
2.1rc3
2.1rc4
2.1
2.1.1
2.1.2
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.*
3.0.0rc1
3.0.0rc2
3.0.0rc3
3.0.0
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"