Vulnerability in Craft CMS (CVE-2026-92591)
Summary
Vulnerability in Craft CMS (CVE-2026-92591). Confidential information can be exposed externally. Mitigation: upgrade to 5.10.13 or later.
Original description
The description as published by the source.
Craft CMS 5.0.0 through 5.10.12 treats a database connection failure as meaning that Craft is not installed, which makes anonymous installer actions — including install/validate-site — reachable on an installed production site whenever PHP remains available but the configured MySQL endpoint does not. The action accepts a site name, serializes it through Site::getName(), and expands ${NAME} expressions using App::env(). An unauthenticated attacker who obtained a guest session cookie and matching CSRF token before the outage and whose session remains valid during it can submit a predictable variable name (for example Craft's conventional CRAFT_SECURITY_KEY) and receive its value, disclosing Craft secrets, process environment variables, $_SERVER entries, or PHP constants such as the security key, database credentials, or API keys. The issue requires an independently occurring database outage; the vulnerability itself provides no way to induce it. Fixed in 5.10.13.
Source: NIST National Vulnerability Database 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-92591 has been found in Craft CMS.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade Craft CMS to 5.10.13 or later.
If unsure, ask your IT team or search "Craft CMS CVE-2026-92591" on the vendor's site.
CVE-2026-92591 (Craft CMS) — CWE-636 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.10.13 — 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-636) exists in Craft CMS.
Check the vendor advisory for the affected versions of Craft CMS.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 5.10.13.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Craft CMS を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Craft CMS to 5.10.13ステージング環境で 5.10.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com