<?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-10-17T23:16:14.505432+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-276768</id>
    <title>EUVD-2026-276768</title>
    <updated>2026-10-17T23:16:14.563395+00:00</updated>
    <content>EUVD-2026-276768</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-276768"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32817</id>
    <title>fkie_cve-2026-32817</title>
    <updated>2026-10-17T23:16:14.563433+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Admidio is an open-source user management solution. In versions 5.0.0 through 5.0.6, the documents and files module does not verify whether the current user has permission to delete folders or files. The folder_delete and file_delete action handlers in modules/documents-files.php only perform a VIEW authorization check (getFolderForDownload / getFileForDownload) before calling delete(), and they never validate a CSRF token. Because the target UUIDs are read from $_GET, deletion can be triggered by a plain HTTP GET request. When the module is in public mode (documents_files_module_enabled = 1) and a folder is marked public (fol_public = true), an unauthenticated attacker can permanently destroy the entire document library. Even when the module requires login, any user with view-only access can delete content they are only permitted to read. This issue has been fixed in version 5.0.7.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32817"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rmpj-3x5m-9m5f</id>
    <title>GHSA-rmpj-3x5m-9m5f — Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion</title>
    <updated>2026-10-17T23:16:14.563478+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: admidio/admidio</p>
<p>## Summary</p>
<p>The documents and files module in Admidio does not verify whether the current user has permission to delete folders or files. The `folder_delete` and `file_delete` action handlers in `modules/documents-files.php` only perform a VIEW authorization check (`getFolderForDownload` / `getFileForDownload`) before calling `delete()`, and they never validate a CSRF token. Because the target UUIDs are read from `$_GET`, deletion can be triggered by a plain HTTP GET request. When the module is in public mode (`documents_files_module_enabled = 1`) and a folder is marked public (`fol_public = true`), an unauthenticated attacker can permanently destroy the entire document library. Even when the module requires login, any user with view-only access can delete content they are only permitted to read.</p>
<p>## Details</p>
<p>### Module Access Check</p>
<p>File: `D:/bugcrowd/admidio/repo/modules/documents-files.php`, lines 72-76</p>
<p>The module only blocks unauthenticated access when the setting is 2 (members-only). When the setting is 1 (public), no login is required to reach any action handler:</p>
<p>```php
if ($gSettingsManager-&gt;getInt('documents_files_module_enabled') === 0) {
    throw new Exception('SYS_MODULE_DISABLED');
} elseif ($gSettingsManager-&gt;getInt('documents_files_module_enabled') === 2 &amp;&amp; !$gValidLogin) {
    throw new Exception('SYS_NO_RIGHTS');
}
```</p>
<p>### Vulnerable Code Path 1: Folder Deletion</p>
<p>File: `D:/bugcrowd/admidio/repo/modules/documents-files.php`, lines 122-133</p>
<p>```php
case 'fol…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-rmpj-3x5m-9m5f"/>
  </entry>
</feed>
