Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS

• CVE-2026-32817: 0.34% estimated exploitation activity in the next 30 days; percentile 27.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The documents and files module in Admidio does not verify whether the current user has permission to delete folders or files. The folderdelete and filedelete 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 (documentsfilesmoduleenabled = 1) and a folder is marked public (folpublic = 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. Details Module Access Check File: D:/bugcrowd/admidio/repo/modules/documents-files.php, lines 72-76 The module only blocks unauthenticated access when the setting is 2 (members-only). When the setting is 1 (public), no…

Published by the source

16 Mar 2026, 21:18 UTC

Last modified by the source

20 Mar 2026, 21:19 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rmpj-3x5m-9m5f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32817

Advisory: Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion
IDs: CVE-2026-32817, GHSA-rmpj-3x5m-9m5f
Record: https://patchnext.com/advisories/cve-2026-32817 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: admidio/admidio 5.0.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist admidio/admidio: affected >= 5.0.0, <= 5.0.6; fixed in 5.0.7

## Suggested inspection (read-only)
- Packagist admidio/admidio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on admidio/admidio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rmpj-3x5m-9m5f (GitHub-reviewed advisory GHSA-rmpj-3x5m-9m5f lists affected ranges: Packagist admidio/admidio >=5.0.0 <=5.0.6)

Commands are suggestions: review each one before running it.