← Back
CVE-2026-47233
medium
CVSS 6.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-862) exists in admidio/admidio. Attackers reach the vulnerable code path via ``d37ca6b27b9674238e58491cf7ba292e66898f15`` without authentication.
📍 Affected scope
admidio/admidio — . Attack surface: `d37ca6b27b9674238e58491cf7ba292e66898f15` / `adm_inventory_item_data` / `adm_inventory_field_options` / `field_delete`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **5.0.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade admidio/admidio to 5.0.10ステージング環境で 5.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
admidio/admidio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.10"}]}]
Packagist
admidio/admidio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.10"}]}]