---
id: CVE-2026-92591
title: >-
  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 P…
summary: >-
  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 P…
severity: medium
cvss: 5.9
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-636
vendor: craftcms
product: cms
affected:
  - cms >= 5.0.0 < 5.10.13
published: '2026-09-16'
updated: '2026-09-17'
sourceUpdated: '2026-09-17T14:17:54.787'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-92591'
references:
  - url: 'https://github.com/craftcms/cms/security/advisories/GHSA-hfjh-gw6x-7pv5'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/craft-cms-5.0.0-before-5.10.13-environment-secret-exposure-via-installer
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-17T13:24:05.702594Z'
ingestedAt: '2026-09-16T22:06:50.930Z'
epss: 0.0024
epssPercentile: 0.15335
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.