CVE-2026-32817: Admidio/admidio Admidio Is Missing Authorization And Vulnerability
CRITICALCVE-2026-32817 is a CRITICAL (CVSS 9.1) admidio is missing authorization and vulnerability (CWE-862: Missing Authorization) affecting Admidio/admidio libraries in the Packagist ecosystem. The issue involves admidio is missing authorization and csrf protection on document and folder deletion. Remediation is available by upgrading affected packages to version 5.0.7.
CVE-2026-32817 at a Glance
Security Impact
CVSS: 9.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).
How to Fix CVE-2026-32817
To remediate this vulnerability, upgrade all affected Admidio/admidio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade admidio/admidio to 5.0.7
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for admidio/admidio
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-32817, inspect your project dependencies for Admidio/admidio:
inspect dependencies for admidio/admidio
Analyze the terminal output to locate any version of Admidio/admidio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.7), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Admidio/admidio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-32817 Affected Admidio/admidio Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
admidio/admidio
|
Packagist |
≥ 5.0.0
< 5.0.7
|
5.0.7
|
References
Frequently Asked Questions
What is CVE-2026-32817?
Which Admidio/admidio versions are affected?
What version fixes CVE-2026-32817?
Is admidio/admidio affected?
What is the CVSS score of CVE-2026-32817?
What CWE is associated with CVE-2026-32817?
How can I check Packagist dependencies for CVE-2026-32817?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rmpj-3x5m-9m5f",
"modified" : "2026-03-20T21:19:26Z",
"published" : "2026-03-16T21:18:10Z",
"aliases" : [ "CVE-2026-32817" ],
"summary" : "Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion",
"details" : "## Summary\n\nThe 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.\n\n## Details\n\n### Module Access Check\n\nFile: `D:/bugcrowd/admidio/repo/modules/documents-files.php`, lines 72-76\n\nThe 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:\n\n```php\nif ($gSettingsManager->getInt('documents_files_module_enabled') === 0) {\n throw new Exception('SYS_MODULE_DISABLED');\n} elseif ($gSettingsManager->getInt('documents_files_module_enabled') === 2 && !$gValidLogin) {\n throw new Exception('SYS_NO_RIGHTS');\n}\n```\n\n### Vulnerable Code Path 1: Folder Deletion\n\nFile: `D:/bugcrowd/admidio/repo/modules/documents-files.php`, lines 122-133\n\n```php\ncase 'folder_delete':\n if ($getFolderUUID === '') {\n throw new Exception('SYS_INVALID_PAGE_VIEW');\n } else {\n $folder = new Folder($gDb);\n $folder->getFolderForDownload($getFolderUUID); // VIEW check only\n\n $folder->delete(); // no CSRF token, no upload/admin check\n echo json_encode(array('status' => 'success'));\n }\n break;\n```\n\nThe target UUID is read exclusively from `$_GET` at line 64:\n\n```php\n$getFolderUUID = admFuncVariableIsValid($_GET, 'folder_uuid', 'uuid', ...);\n```\n\n### Vulnerable Code Path 2: File Deletion\n\nFile: `D:/bugcrowd/admidio/repo/modules/documents-files.php`, lines 150-161\n\n```php\ncase 'file_delete':\n if ($getFileUUID === '') {\n throw new Exception('SYS_INVALID_PAGE_VIEW');\n } else {\n $file = new File($gDb);\n $file->getFileForDownload($getFileUUID); // VIEW check only\n\n $file->delete(); // no CSRF token, no upload/admin check\n echo json_encode(array('status' => 'success'));\n }\n break;\n```\n\nSame pattern as `folder_delete`. The file UUID is also read from `$_GET` (line 69).\n\n### getFolderForDownload Grants VIEW Access to Public Folders Without Login\n\nFile: `D:/bugcrowd/admidio/repo/src/Documents/Entity/Folder.php`, lines 432-438\n\n```php\n// If the folder is public (and the file is not locked) => allow\nif ($this->getValue('fol_public') && !$this->getValue('fol_locked')) {\n return true;\n}\n```\n\nThis is the correct check for granting VIEW access to public folders. It is not an appropriate gate for a destructive delete operation.\n\n### Contrast with Other Write Operations (Properly Protected)\n\nAll other write operations in `documents-files.php` route through `DocumentsService`, which validates the CSRF token via `getFormObject($_POST['adm_csrf_token'])` before any mutation (DocumentsService.php lines 278, 332, 386, 448). The delete cases bypass this service entirely and receive no equivalent protection.\n\n### Folder::delete() Is Recursive and Permanent\n\nFile: `D:/bugcrowd/admidio/repo/src/Documents/Entity/Folder.php`, lines 213-259\n\n`Folder::delete()` recursively removes all sub-folders and files from both the database and the physical filesystem. There is no soft-delete or trash mechanism. A single call to `folder_delete` on the root folder permanently destroys the entire document library.\n\n### UI Shows Delete Buttons Only to Authorized Users (Not Enforced Server-Side)\n\nFile: `D:/bugcrowd/admidio/repo/src/UI/Presenter/DocumentsPresenter.php`, lines 546, 589\n\nThe presenter renders delete action links only when the user has upload rights (`hasUploadRight()`). This client-side restriction is not enforced server-side. Any HTTP client can send the GET request directly.\n\n## PoC\n\n**Scenario 1: Unauthenticated deletion of a public folder (zero credentials required)**\n\nPrerequisites: `documents_files_module_enabled = 1`, target folder has `fol_public = true`.\n\nStep 1: Discover folder UUIDs by fetching the public document list (no login needed):\n\n```\ncurl \"https://TARGET/adm_program/modules/documents-files.php?mode=list\"\n```\n\nStep 2: Delete the entire folder tree permanently:\n\n```\ncurl \"https://TARGET/adm_program/modules/documents-files.php?mode=folder_delete&folder_uuid=<FOLDER_UUID>\"\n```\n\nExpected response: `{\"status\":\"success\"}`\n\nThe folder, all its sub-folders, and all their files are permanently removed from the database and filesystem. No authentication or token is required.\n\n**Scenario 2: Authenticated view-only member deletes any accessible file**\n\nPrerequisites: `documents_files_module_enabled = 2` (members-only). Attacker has a regular member account with view rights to the target folder but no upload rights.\n\n```\ncurl \"https://TARGET/adm_program/modules/documents-files.php?mode=file_delete&file_uuid=<FILE_UUID>\" \\\n -H \"Cookie: ADMIDIO_SESSION_ID=<view_only_session>\"\n```\n\nExpected response: `{\"status\":\"success\"}`\n\n**Scenario 3: Cross-site GET CSRF via image tag**\n\nBecause deletion uses a plain GET request with no token, an attacker can embed the following in any HTML email or web page. When a logged-in Admidio member views the page, their browser fetches the URL with the session cookie attached:\n\n```html\n<img src=\"https://TARGET/adm_program/modules/documents-files.php?mode=folder_delete&folder_uuid=<UUID>\" width=\"1\" height=\"1\">\n```\n\n## Impact\n\n- **Unauthenticated Data Destruction:** When the module is in public mode and any folder is marked public, an unauthenticated remote attacker can permanently delete any or all documents and folders. No credentials or tokens are required.\n- **Privilege Escalation (View to Delete):** Any logged-in member with view-only access can delete content they are only permitted to read, bypassing the `hasUploadRight()` permission boundary.\n- **Cross-Site CSRF:** Because UUIDs appear in page URLs visible to authenticated users, an attacker can embed a GET-based CSRF payload in phishing content to trigger deletion on behalf of any victim.\n- **No Recovery Path:** `Folder::delete()` and `File::delete()` are permanent operations. The only recovery is from a database and filesystem backup.\n- **Full Organizational Impact:** Deletion of the root documents folder recursively removes the entire document library of the organization.\n\n## Recommended Fix\n\n### Fix 1: Add authorization check and CSRF token validation to both delete handlers\n\n```php\ncase 'folder_delete':\n SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);\n if ($getFolderUUID === '') {\n throw new Exception('SYS_INVALID_PAGE_VIEW');\n }\n $folder = new Folder($gDb);\n $folder->getFolderForDownload($getFolderUUID);\n if (!$gCurrentUser->isAdministratorDocumentsFiles() && !$folder->hasUploadRight()) {\n throw new Exception('SYS_NO_RIGHTS');\n }\n $folder->delete();\n echo json_encode(array('status' => 'success'));\n break;\n\ncase 'file_delete':\n SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);\n if ($getFileUUID === '') {\n throw new Exception('SYS_INVALID_PAGE_VIEW');\n }\n $file = new File($gDb);\n $file->getFileForDownload($getFileUUID);\n $parentFolder = new Folder($gDb);\n $parentFolder->readDataById((int)$file->getValue('fil_fol_id'));\n if (!$gCurrentUser->isAdministratorDocumentsFiles() && !$parentFolder->hasUploadRight()) {\n throw new Exception('SYS_NO_RIGHTS');\n }\n $file->delete();\n echo json_encode(array('status' => 'success'));\n break;\n```\n\n### Fix 2: Move folder_uuid and file_uuid to POST parameters for delete operations\n\nReading the UUID from `$_GET` enables GET-based CSRF. Moving to `$_POST` and validating the CSRF token together closes both issues simultaneously.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "admidio/admidio"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "5.0.0"
}, {
"fixed" : "5.0.7"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 5.0.6"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Admidio/admidio/security/advisories/GHSA-rmpj-3x5m-9m5f"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32817"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Admidio/admidio"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-862" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-16T21:18:10Z",
"nvd_published_at" : "2026-03-20T02:16:35Z"
}
}