Admidio: Any logged-in user can delete inventory fields via mode=field_delete — incomplete fix of #2024

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-47233: 0.31% estimated exploitation activity in the next 30 days; percentile 24.06 (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 Commit d37ca6b27b9674238e58491cf7ba292e66898f15 ("Delete item not check admin rights #2024", 2026-04-12) added a missing isAdministratorInventory() gate to case 'itemdelete': in modules/inventory.php. The same fix was not applied to the sibling case 'fielddelete': handler, which destroys an entire inventory field definition, cascading to every adminventoryitemdata row that referenced that field and every adminventoryfieldoptions entry. The handler validates only a session-bound CSRF token; there is no isAdministratorInventory() check at the controller level, and Admidio\Inventory\Entity\ItemField::delete() does not enforce one at the entity level either (unlike its sibling ItemField::save(), which does check $gCurrentUser-isAdministrator()). Any user who can log in to the site can permanently destroy a non-system inventory field by sending one POST. Details Vulnerable Code modules/inventory.php mode dispatch at the top of the file: inventorymoduleenabled=2 is the default…

Published by the source

29 May 2026, 22:09 UTC

Last modified by the source

29 May 2026, 22:09 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xw54-c3mx-9pm3

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

# Patch Next advisory brief: CVE-2026-47233

Advisory: Admidio: Any logged-in user can delete inventory fields via `mode=field_delete` — incomplete fix of #2024
IDs: CVE-2026-47233, GHSA-xw54-c3mx-9pm3
Record: https://patchnext.com/advisories/cve-2026-47233 (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-xw54-c3mx-9pm3 (GitHub-reviewed advisory GHSA-xw54-c3mx-9pm3 lists affected ranges: Packagist admidio/admidio >=0 <=5.0.9)

Commands are suggestions: review each one before running it.