# CVE-2026-111914: Admidio 5.0.11 before 5.0.16 Broken Access Control via inventory_data.php

> Authenticated users can bypass access controls to read all inventory items and keeper names in Admidio, even when the module is disabled.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-pf3j-3gfx-w49c

## What is CVE-2026-111914?

CVE-2026-111914 is a high-severity missing authorization vulnerability in admidio, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Admidio from 5.0.11 before 5.0.16 contains a broken access control vulnerability in modules/inventory/inventory_data.php that allows authenticated users to bypass the inventory_module_enabled restriction. Attackers with any valid login can request the DataTables JSON feed to read every inventory item and keeper names, even when the module is disabled.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-111914 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111914 is a high-severity missing authorization vulnerability in admidio, published on 17 Oct 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-111914 exists.

Affected product: admidio. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111914/ (Markdown: https://insights.sbomify.com/CVE-2026-111914/index.md)
```

## Sources

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

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