Quick answers
- Is CVE-2026-47231 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47231 being exploited in the wild.
- How severe is CVE-2026-47231?
- High severity, with a CVSS score of 8.1, published 29 May 2026.
- Which products and versions are affected?
- Admidio <= 5.0.9; admidio/admidio (Packagist) <= 5.0.9, ECOSYSTEM:introduced=0,fixed=5.0.10.
- Is there a fix for CVE-2026-47231?
- Yes. admidio/admidio (Packagist): upgrade to 5.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47231 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-47231?
- Check whether you run Admidio or admidio/admidio (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- admidio/admidio (Packagist): upgrade to 5.0.10 or later
composer require admidio/admidio:^5.0.10
Technical details
An Insecure Direct Object Reference (IDOR) exists in `modules/documents-files.php` within the `move_save` mode. The application validates permissions based on a `folder_uuid` provided in the URL, but the subsequent file move operation uses a separate `file_uuid` without verifying if the user has rights to the file's source folder. By providing a `folder_uuid` for a folder they control and a `file_uuid` for a restricted file, an attacker can move the file to a location where they have download permissions. This bypasses folder-level access controls and allows for unauthorized data exfiltration and file relocation. The issue is fixed in version 5.0.10.
Affected products
- Admidio Admidio <= 5.0.9
Identifiers
- CVE-2026-47231
- GHSA-x628-457g-2pw9
Timeline
- 2026-05-25: disclosed
- 2026-05-29: advisory
- 2026-05-29: patched: Fixed in version 5.0.10