{"answers":{"affected":"4 open source packages ship an affected version, including craftcms/cms.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55792 exists.","fix":"Upgrade craftcms/cms to a fixed version for your release line: 4.18.0 or 5.10.0.","what":"CVE-2026-55792 is a medium-severity vulnerability in craftcms cms, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55792 and fix it if it is affected.\n\nWhat it is: CVE-2026-55792 is a medium-severity vulnerability in craftcms cms, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55792 exists.\n\nAffected packages and fixed versions:\n- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.18.0\n- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.18.0\n- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.10.0\n- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.10.0\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-55792/ (Markdown: https://insights.sbomify.com/CVE-2026-55792/index.md)","id":"CVE-2026-55792","markdown":"https://insights.sbomify.com/CVE-2026-55792/index.md","name":"CVE-2026-55792","record":{"aliases":["GHSA-287w-mxq6-x2cp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Craft CMS","requires_auth":"low_privilege","summary":"Craft CMS allows privileged users to read sensitive files like .env via email templates, potentially leading to admin account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Craft CMS is a content management system (CMS). In versions starting from 4.0.0-RC1 and prior to 4.18.0, and 5.0.0-RC1 and above, prior to 5.10.0, the dataUrl() Twig function is included in Craft’s Twig sandbox allowlist, allowing any control panel user granted the utility:system-messages permission to embed a file-reading payload into system email templates. When those emails are sent, the server reads the target file and returns its contents as a base64-encoded data URL embedded in the email body. The .env file, which typically contains the database password, CRAFT_SECURITY_KEY, and third-party API keys, passes all of Craft’s existing dataUrl() protection checks and is fully exfiltrated. Obtaining CRAFT_SECURITY_KEY enables an attacker to forge session tokens and escalate to full admin account takeover. This issue has been fixed in versions 4.18.0 and 5.10.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Craft CMS: Sensitive File Disclosure / Server-Side File Read","id":"CVE-2026-55792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Craft CMS: Stored XSS via Structure entry title in table view","id":"CVE-2026-55793"},"packages":[{"ecosystem":"Packagist","fixed":["4.18.0"],"introduced":["4.0.0-RC1"],"last_affected":[],"package":"craftcms/cms","purl":null,"source":"GHSA-287w-mxq6-x2cp"},{"ecosystem":"Packagist","fixed":["4.18.0"],"introduced":["4.0.0-RC1"],"last_affected":[],"package":"craftcms/cms","purl":"pkg:composer/craftcms/cms","source":"GHSA-287w-mxq6-x2cp"},{"ecosystem":"Packagist","fixed":["5.10.0"],"introduced":["5.0.0-RC1"],"last_affected":[],"package":"craftcms/cms","purl":null,"source":"GHSA-287w-mxq6-x2cp"},{"ecosystem":"Packagist","fixed":["5.10.0"],"introduced":["5.0.0-RC1"],"last_affected":[],"package":"craftcms/cms","purl":"pkg:composer/craftcms/cms","source":"GHSA-287w-mxq6-x2cp"}],"prev":{"headline":"Craft CMS: Blind SSRF and Arbitrary JavaScript Injection via Host Header Poisoning in actionResourceJs","id":"CVE-2026-55791"},"products":["cms"],"published":"2026-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-02","vendors":["craftcms"]},"summary":"Craft CMS allows privileged users to read sensitive files like .env via email templates, potentially leading to admin account takeover.","url":"https://insights.sbomify.com/CVE-2026-55792/"}