Cross-Site Request Forgery (CSRF) in admidio/admidio (CVE-2026-47228)
Summary
Vulnerability in admidio/admidio (CVE-2026-47228). Data can be tampered with by attackers. Exploitable via GET /modules/registration.php. Mitigation: upgrade to 5.0.10 or later.
Original description
The description as published by the source.
Summary
modules/registration.php mode send_login regenerates a random password for user_uuid_assigned, stores its bcrypt hash in adm_users.usr_password, and emails the cleartext to that user. Every other state-changing mode in the same file (assign_member, assign_user, delete_user, create_user) calls SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']) first; the send_login branch does not. A page visited by a registration-administrator can issue the request as a top-level navigation, the browser sends the admin's SameSite=Lax cookies, and the server resets the chosen user's password without any further interaction from the admin.
Details
Vulnerable Code
modules/registration.php:124-138:
} elseif ($getMode === 'send_login') {
// User already exists and has a login than sent access data with a new password
$user = new User($gDb, $gProfileFields);
$user->readDataByUuid($getUserUUIDAssigned);
$user->sendNewPassword();
// delete the registration because it isn't necessary anymore
$registrationUser->notSendEmail();
$registrationUser->delete();
admRedirect(ADMIDIO_URL.FOLDER_MODULES.'/registration.php');
// => EXIT
}
The four sibling branches all begin with SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']); — for example delete_user at lines 110-118:
} elseif ($getMode === 'delete_user') {
// check the CSRF token of the form against the session token
SecurityUt…
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-47228 has been found in admidio/admidio.
Attackers can target a specific entry point like GET /modules/registration.php over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.2/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-47228" on the vendor's site.
CVE-2026-47228 (admidio/admidio) — CWE-352 / CVSS v3 5.2
Attack vector: remote (network-reachable)
Attack surface: GET /modules/registration.php / send_login / user_uuid_assigned / adm_users.usr_password
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.
CSRF (CWE-352) exists in admidio/admidio. Attackers reach the vulnerable code path via GET /modules/registration.php.
Check the vendor advisory for the affected versions of admidio/admidio. Attack surface: GET /modules/registration.php / send_login / user_uuid_assigned / adm_users.usr_password.
Severity: Medium (CVSS 5.2/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 GET /modules/registration.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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /modules/registration.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /modules/registration.phpへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade admidio/admidio to 5.0.10ステージング環境で 5.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /modules/registration.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com