<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T20:39:44.492469+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-409024</id>
    <title>EUVD-2026-409024</title>
    <updated>2026-11-22T20:39:44.494716+00:00</updated>
    <content>EUVD-2026-409024</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-409024"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-69131</id>
    <title>fkie_cve-2026-69131</title>
    <updated>2026-11-22T20:39:44.494747+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-69131"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vf85-8ff2-3r9w</id>
    <title>GHSA-vf85-8ff2-3r9w — django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions</title>
    <updated>2026-11-22T20:39:44.494780+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django-filer</p>
<p>## Summary</p>
<p>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.</p>
<p>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.</p>
<p>## Affected versions</p>
<p>- django-filer `&lt;= 3.4.4` (verified end-to-end on 3.4.4 and on `master` prior to   the fix).</p>
<p>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.</p>
<p>## Patched versions</p>
<p>- Fixed in PR [#1605](https://github.com/django-cms/django-filer/pull/1605).   Upgrade to the first release containing that commit (`3.5.0` or later).</p>
<p>## Details</p>
<p>The `delete_files_or_folders` admin action in `filer/admin/folderadmin.py` authorized deletion using only:</p>
<p>1. `self.has_delete_permission(request)`…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vf85-8ff2-3r9w"/>
  </entry>
</feed>
