Admidio module-administrator can delete or reorder categories owned by other modules via dead authorization check in modules/categories.php

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-47227: 0.33% estimated exploitation activity in the next 30 days; percentile 25.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. 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. Details vulnerable code modules/categories.php:40-61: The inarray($getType, array('edit','save','delete')) test compares the…

Published by the source

29 May 2026, 21:57 UTC

Last modified by the source

29 May 2026, 21:57 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rwjr-qjj3-mq2f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47227

Advisory: Admidio module-administrator can delete or reorder categories owned by other modules via dead authorization check in `modules/categories.php`
IDs: CVE-2026-47227, GHSA-rwjr-qjj3-mq2f
Record: https://patchnext.com/advisories/cve-2026-47227 (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: Medium (CVSS 6.5)
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-rwjr-qjj3-mq2f (GitHub-reviewed advisory GHSA-rwjr-qjj3-mq2f lists affected ranges: Packagist admidio/admidio >=0 <=5.0.9)

Commands are suggestions: review each one before running it.