Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/craftcms/cms/security/advisories/GHSA-hfjh-gw6x-7pv5
- https://www.vulncheck.com/advisories/craft-cms-5.0.0-before-5.10.13-environment-
FAQ
What is CVE-2026-92591?
CVE-2026-92591 is a vulnerability with a CVSS score of 5.9 (MEDIUM). 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...
How severe is CVE-2026-92591?
CVE-2026-92591 has been rated MEDIUM with a CVSS base score of 5.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-92591?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.