← Back
CVE-2026-47229
medium
CVSS 5.4
Cross-Site Request Forgery (CSRF) in admidio/admidio (CVE-2026-47229)
Summary
vulnerability in admidio/admidio (CVE-2026-47229). Risk of unauthorized operations or information disclosure. Exploitable via `GET /modules/sso/clients.php`. Mitigation: upgrade to `5.0.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47229** has been found in admidio/admidio.
Attackers can target a specific entry point like `GET /modules/sso/clients.php` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/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-47229" on the vendor's site.
CVE-2026-47229 (admidio/admidio) — CWE-352 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /modules/sso/clients.php / `adm_csrf_token` / `enable` / `smc_enabled`
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
**CSRF** (CWE-352) exists in admidio/admidio. Attackers reach the vulnerable code path via `GET /modules/sso/clients.php` without authentication.
📍 Affected scope
admidio/admidio — . Attack surface: GET /modules/sso/clients.php / `adm_csrf_token` / `enable` / `smc_enabled`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 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 `GET /modules/sso/clients.php` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /modules/sso/clients.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /modules/sso/clients.php` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade admidio/admidio to 5.0.10ステージング環境で 5.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /modules/sso/clients.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで 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"}]}]