Authorization Flaw in craftcms/cms (CVE-2026-32267)
Summary
Vulnerability in craftcms/cms (CVE-2026-32267). Risk of unauthorized operations or information disclosure. Exploitable via _hadToken. Mitigation: upgrade to 5.9.12 or later.
Original description
The description as published by the source.
Craft CMS is a content management system (CMS). From version 4.0.0-RC1 to before version 4.17.6 and from version 5.0.0-RC1 to before version 5.9.12, a low-privilege user (or an unauthenticated user who has been sent a shared URL) can escalate their privileges to admin by abusing UsersController->actionImpersonateWithToken. This issue has been patched in versions 4.17.6 and 5.9.12.
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-32267 has been found in craftcms/cms.
Attackers can target a specific entry point like _hadToken over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade craftcms/cms to 5.9.12 or later.
If unsure, ask your IT team or search "craftcms/cms CVE-2026-32267" on the vendor's site.
CVE-2026-32267 (craftcms/cms) — CWE-863
Attack surface: _hadToken / actionImpersonateWithToken
Patched: 5.9.12 — 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.
Incorrect authorization (CWE-863) exists in craftcms/cms. Attackers reach the vulnerable code path via _hadToken.
Check the vendor advisory for the affected versions of craftcms/cms. Attack surface: _hadToken / actionImpersonateWithToken.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.9.12.
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 'craftcms/cms' . 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 'craftcms/cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
craftcms/cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade craftcms/cms to 5.9.12ステージング環境で 5.9.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com