Admidio has IDOR in documents-files.php mode=move_save that lets any folder-uploader exfiltrate files from private folders
CVE-2026-47231GHSA-x628-457g-2pw9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (admidio/admidio 5.0.10), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist admidio/admidio
- Affected
- <= 5.0.9
- Fixed in
- 5.0.10
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-x628-457g-2pw9 lists affected ranges: Packagist admidio/admidio >=0 <=5.0.9
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- EPSS
- CVE-2026-47231: 0.35% estimated exploitation activity in the next 30 days; percentile 28.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary modules/documents-files.php gates state-changing modes by checking that the actor has hasUploadRight() on the URL parameter folderuuid. The movesave handler then operates on a separate URL parameter fileuuid and calls File::moveToFolder($destFolderUUID). File::moveToFolder() checks the upload right on the destination folder but never on the source folder containing the file. As a result, any user who can upload to any single folder can move any file from any other folder — including private folders to which they have no view rights — into a folder they control, and then download it. Confidentiality is broken (private file contents leak) and integrity is broken (the file is removed from the original location). Details Vulnerable Code modules/documents-files.php:79-89 — top-level rights check binds to URL folderuuid: modules/documents-files.php:187-204 — the movesave branch loads the file by UUID without revalidating the file's actual parent folder:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-x628-457g-2pw9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-47231 Advisory: Admidio has IDOR in `documents-files.php` `mode=move_save` that lets any folder-uploader exfiltrate files from private folders IDs: CVE-2026-47231, GHSA-x628-457g-2pw9 Record: https://patchnext.com/advisories/cve-2026-47231 (revision 1, source checked 26 Oct 2026, 14:48 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.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.10. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist admidio/admidio: affected <= 5.0.9; fixed in 5.0.10 ## 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-x628-457g-2pw9 (GitHub-reviewed advisory GHSA-x628-457g-2pw9 lists affected ranges: Packagist admidio/admidio >=0 <=5.0.9) Commands are suggestions: review each one before running it.
Loading voting…