# CVE-2026-47227: Admidio module-administrator can delete or reorder categories owned by other modules via dead authorization check in `modules/categories.php`

> A module administrator can delete or reorder categories belonging to other modules due to a dead authorization check in Admidio.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-rwjr-qjj3-mq2f

## What is CVE-2026-47227?

CVE-2026-47227 is a medium-severity missing authorization vulnerability in admidio, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Admidio is an open-source user management solution. `modules/categories.php` checks that the supplied `type` parameter (`ANN`, `EVT`, `ROL`, `USF`, …) corresponds to a module the actor administers. The follow-up "is this specific category editable by me" check at lines 56-61 is dead code because it compares `$getType` (a category-type code) against mode names (`edit`/`save`/`delete`); the condition is permanently false, so `$category->isEditable()` is never invoked. Prior to version 5.0.10, the `delete`, `sequence`, and `save` switch cases load the category by the supplied UUID and act on it without re-checking that the category belongs to a module the actor administers. A user holding only one module-administrator right can therefore destroy or reorder empty categories belonging to *other* modules — for example, an announcements administrator can delete role categories, profile-field categories, or weblink categories that they have no right to touch. Version 5.0.10 fixes the issue.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-47227?

2 open source packages ship an affected version, including admidio/admidio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | All versions | 5.0.10 |
| `admidio/admidio` | Packagist | All versions | 5.0.10 |

## How do I fix CVE-2026-47227?

Upgrade admidio/admidio to 5.0.10 or later.

## Is CVE-2026-47227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47227 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47227 and fix it if it is affected.

What it is: CVE-2026-47227 is a medium-severity missing authorization vulnerability in admidio, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47227 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.10
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47227/ (Markdown: https://insights.sbomify.com/CVE-2026-47227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47227
- OSV: https://osv.dev/vulnerability/CVE-2026-47227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47227/
Summaries are generated and may contain mistakes; the official description above is the record.