{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92591 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92591 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92591 is a high-severity vulnerability in craftcms cms, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92591 and fix it if it is affected.\n\nWhat it is: CVE-2026-92591 is a high-severity vulnerability in craftcms cms, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92591 in the wild and no public exploit code.\n\nAffected product: craftcms cms. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-92591/ (Markdown: https://insights.sbomify.com/CVE-2026-92591/index.md)","id":"CVE-2026-92591","markdown":"https://insights.sbomify.com/CVE-2026-92591/index.md","name":"CVE-2026-92591","record":{"aliases":["GHSA-fq6c-26cc-63cr","GHSA-hfjh-gw6x-7pv5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Craft CMS","requires_auth":"none","summary":"An unauthenticated attacker can expose sensitive environment variables and secrets if a database outage occurs, allowing access to credentials and keys.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Craft CMS 5.0.0 before 5.10.13 Environment Secret Exposure via Installer","id":"CVE-2026-92591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Craft CMS before 4.18.6 Remote Code Execution via signed cookie","id":"CVE-2026-92592"},"packages":[],"prev":{"headline":"Craft CMS 5.7.0 before 5.10.13 Stored XSS via Generated Fields","id":"CVE-2026-92590"},"products":["cms"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["craftcms"]},"summary":"An unauthenticated attacker can expose sensitive environment variables and secrets if a database outage occurs, allowing access to credentials and keys.","url":"https://insights.sbomify.com/CVE-2026-92591/"}