CVE
django-filer IDOR in folder permissions allows unauthorized deletion
- Exploited
- No known exploitation
- Fix
- Fixed in 3.5.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.5.0.
Summary
In django-filer, a logged-in staff user with global delete permission but read-only access to a folder can delete that folder's files, subfolders, and their contents over the network. This affects only deployments that enable per-folder permissions. The flaw does not expose file contents.
Original description
django-filer is a file and image management application for Django. Prior to 3.5.0, the delete_files_or_folders action in filer/admin/folderadmin.py checks global Django model-level deletion permission but omits check_folder_edit_permissions and check_files_edit_permissions when FILER_ENABLE_PERMISSIONS is enabled. An authenticated staff user who has a global delete_file, delete_folder, or delete_image 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.5.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-69131 (django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-69131 (entry last updated 2026-11-18):
Affected:
- django-cms django-filer: fixed in 3.5.0
Fixed versions: 3.5.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69131 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69131 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/django-cms/django-filer/security/advisories/GHSA-vf85-8ff2-3r9w
- https://github.com/django-cms/django-filer/pull/1605
- https://github.com/django-cms/django-filer/commit/29d20ec0de13d7f77fa2cea93166f8d50a3f508d
- https://github.com/django-cms/django-filer/commit/742ba4c3094dd75e586ca3a05e6ad2703de4553b
- https://github.com/django-cms/django-filer/releases/tag/3.5.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-69131
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69131"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- django-cms django-filer
fixed in 3.5.0
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · django-cms/django-filer · Advisory GHSA-vf85-8ff2-3r9w |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-69131 |
| Record | NVD · CVE-2026-69131 |
| Other links 4 | |
| Repository | GitHub · django-cms/django-filer · Pull request #1605 |
| Repository | GitHub · django-cms/django-filer · Commit 29d20ec0 |
| Repository | GitHub · django-cms/django-filer · Commit 742ba4c3 |
| Repository | GitHub · django-cms/django-filer · Release 3.5.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-69131
Is CVE-2026-69131 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-69131?
django-filer: before 3.5.0.Source: cve.now feed data
How do I fix CVE-2026-69131?
Upgrade to a fixed version: 3.5.0.Source: cve.now feed data