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

Advisory record · `GHSA-xw54-c3mx-9pm3`

- **Identifiers:** `GHSA-xw54-c3mx-9pm3` · `CVE-2026-47233` · `PKSA-k742-4y2v-1nnc`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) · [CWE-1281](https://cwe.mitre.org/data/definitions/1281.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-1281](https://agentprime.io/advisories/tag/cwe-1281.md)
- **Published:** 29 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 May 2026, 22:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `admidio/admidio` (Packagist): affected `<5.0.10`; fixed in `5.0.10`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Admidio versions before 5.0.10 let any logged-in user permanently delete a custom inventory field, along with all item values and dropdown options stored for it. The field deletion action checks only a session token and not inventory administrator rights, and the default inventory module setting lets any logged-in member reach it. Upgrade to Admidio 5.0.10, which contains the fix.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 24th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:58 UTC: First seen by agentprime
- 31 Oct 2026, 13:58 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xw54-c3mx-9pm3)

## Sources

- [GitHub Advisory Database: GHSA-xw54-c3mx-9pm3](https://github.com/advisories/GHSA-xw54-c3mx-9pm3)
- [OSV: GHSA-xw54-c3mx-9pm3](https://osv.dev/vulnerability/GHSA-xw54-c3mx-9pm3)
- <https://github.com/Admidio/admidio/security/advisories/GHSA-xw54-c3mx-9pm3>
- <https://github.com/Admidio/admidio>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xw54-c3mx-9pm3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xw54-c3mx-9pm3/>. Everything for agents: <https://agentprime.io/llms.txt>.