Vulnerability in admidio/admidio (CVE-2026-47233)
Summary
Vulnerability in admidio/admidio (CVE-2026-47233). Data can be tampered with by attackers. Exploitable via d37ca6b27b9674238e58491cf7ba292e66898f15. Mitigation: upgrade to 5.0.10 or later.
Original description
The description as published by the source.
Summary
Commit d37ca6b27b9674238e58491cf7ba292e66898f15 ("Delete item not check admin rights #2024", 2026-04-12) added a missing isAdministratorInventory() gate to case 'item_delete': in modules/inventory.php. The same fix was not applied to the sibling case 'field_delete': handler, which destroys an entire inventory field definition, cascading to every adm_inventory_item_data row that referenced that field and every adm_inventory_field_options 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:
// modules/inventory.php:64-72 (top-level rights gate)
if ($gSettingsManager->getInt('inventory_module_enabled') === 0) {
throw new Exception('SYS_MODULE_DISABLED');
} elseif ($gSettingsManager->getInt('inventory_module_enabled') === 2 && !$gValidLogin
|| ($gSettingsManager->getInt('inventory_module_enabled') === 3 && !$gCurrentUser->isAdministratorInventory())
|| ($gSettingsManager->getInt('inventory_module_enabled') === 4 && !InventoryPresenter::isCurrentUserKeeper() && !…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47233 has been found in admidio/admidio.
Attackers can target a specific entry point like d37ca6b27b9674238e58491cf7ba292e66898f15 over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade admidio/admidio to 5.0.10 or later.
If unsure, ask your IT team or search "admidio/admidio CVE-2026-47233" on the vendor's site.
CVE-2026-47233 (admidio/admidio) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: d37ca6b27b9674238e58491cf7ba292e66898f15 / adm_inventory_item_data / adm_inventory_field_options / field_delete
Patched: 5.0.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in admidio/admidio. Attackers reach the vulnerable code path via d37ca6b27b9674238e58491cf7ba292e66898f15.
Check the vendor advisory for the affected versions of admidio/admidio. Attack surface: d37ca6b27b9674238e58491cf7ba292e66898f15 / adm_inventory_item_data / adm_inventory_field_options / field_delete.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 5.0.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'admidio/admidio' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'admidio/admidio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
admidio/admidioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade admidio/admidio to 5.0.10ステージング環境で 5.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web security-advisories@github.com