Vulnerability in admidio/admidio (CVE-2026-32817)
Summary
Vulnerability in admidio/admidio (CVE-2026-32817). Data can be tampered with by attackers. Exploitable via folder_delete. Mitigation: upgrade to 5.0.7 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32817 has been found in admidio/admidio.
Attackers can target a specific entry point like folder_delete over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade admidio/admidio to 5.0.7 or later.
If unsure, ask your IT team or search "admidio/admidio CVE-2026-32817" on the vendor's site.
CVE-2026-32817 (admidio/admidio) — CWE-862
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: folder_delete / file_delete / getFolderForDownload / getFileForDownload
Patched: 5.0.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in admidio/admidio. Attackers reach the vulnerable code path via folder_delete without authentication.
Check the vendor advisory for the affected versions of admidio/admidio. Attack surface: folder_delete / file_delete / getFolderForDownload / getFileForDownload.
Severity: ?. Data can be tampered with by attackers.
Update to 5.0.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'admidio/admidio' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'admidio/admidio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
admidio/admidioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade admidio/admidio to 5.0.7ステージング環境で 5.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com