<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Nov 2026 20:32:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-69131 — django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-69131</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; django-cms django-filer&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; django-cms django-filer&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-69131</guid>
    </item>
  </channel>
</rss>
