Quick answers
- Is CVE-2026-47227 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47227 being exploited in the wild.
- How severe is CVE-2026-47227?
- Medium severity, with a CVSS score of 6.5, 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-47227?
- 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-47227 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-47227?
- 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
A vulnerability exists in `modules/categories.php` due to a 'dead code' authorization check. The script validates that a user has rights for a specific module type (e.g., 'ANN' for announcements) but fails to verify if the specific category being modified (identified by UUID) actually belongs to that module. A logic error in an `in_array` check compares the category type against action modes ('edit', 'save', 'delete'), which always evaluates to false, bypassing the `$category->isEditable()` check. An attacker with any single module-admin privilege can perform POST requests to delete or modify categories of any other type. This is fixed in version 5.0.10.
Affected products
- Admidio Admidio <= 5.0.9
Identifiers
- CVE-2026-47227
- GHSA-rwjr-qjj3-mq2f
Timeline
- 2026-05-25: disclosed
- 2026-05-29: advisory