CVE-2026-55792: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in craftcms cms
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.
AI Analysis
Technical Summary
The vulnerability in Craft CMS involves the dataUrl() Twig function being included in the Twig sandbox allowlist for control panel users with the utility:system-messages permission. This allows such users to embed payloads in system email templates that read arbitrary files on the server and embed their contents as base64-encoded data URLs in outgoing emails. The .env file, which contains sensitive credentials and keys, can be fully exfiltrated despite existing protection checks. Obtaining the CRAFT_SECURITY_KEY enables attackers to forge session tokens and escalate privileges to full administrative control. The vulnerability affects versions starting from 4.0.0-RC1 up to but not including 4.18.0, and 5.0.0-RC1 up to but not including 5.10.0. The issue has been fixed in versions 4.18.0 and 5.10.0.
Potential Impact
An attacker with the utility:system-messages permission can read arbitrary files on the server by embedding file-reading payloads in system email templates. This leads to exposure of sensitive information such as database passwords, security keys, and API keys stored in the .env file. With the CRAFT_SECURITY_KEY, an attacker can forge session tokens, resulting in full administrative account takeover. This elevates the risk from a limited permission user to a complete compromise of the CMS.
Mitigation Recommendations
Upgrade Craft CMS to version 4.18.0 or later if using the 4.x branch, or to version 5.10.0 or later if using the 5.x branch. These versions contain the fix that removes the vulnerability. Until upgraded, restrict the utility:system-messages permission to trusted users only, as this permission enables exploitation of the vulnerability. Patch status is confirmed fixed in the specified versions.
CVE-2026-55792: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in craftcms cms
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.
CVSS v4.0
Score 6.0medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Craft CMS involves the dataUrl() Twig function being included in the Twig sandbox allowlist for control panel users with the utility:system-messages permission. This allows such users to embed payloads in system email templates that read arbitrary files on the server and embed their contents as base64-encoded data URLs in outgoing emails. The .env file, which contains sensitive credentials and keys, can be fully exfiltrated despite existing protection checks. Obtaining the CRAFT_SECURITY_KEY enables attackers to forge session tokens and escalate privileges to full administrative control. The vulnerability affects versions starting from 4.0.0-RC1 up to but not including 4.18.0, and 5.0.0-RC1 up to but not including 5.10.0. The issue has been fixed in versions 4.18.0 and 5.10.0.
Potential Impact
An attacker with the utility:system-messages permission can read arbitrary files on the server by embedding file-reading payloads in system email templates. This leads to exposure of sensitive information such as database passwords, security keys, and API keys stored in the .env file. With the CRAFT_SECURITY_KEY, an attacker can forge session tokens, resulting in full administrative account takeover. This elevates the risk from a limited permission user to a complete compromise of the CMS.
Mitigation Recommendations
Upgrade Craft CMS to version 4.18.0 or later if using the 4.x branch, or to version 5.10.0 or later if using the 5.x branch. These versions contain the fix that removes the vulnerability. Until upgraded, restrict the utility:system-messages permission to trusted users only, as this permission enables exploitation of the vulnerability. Patch status is confirmed fixed in the specified versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-17T14:40:28.380Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a45a80827e9c797195b4144
Added to database: 07/01/2026, 23:51:36 UTC
Last enriched: 07/09/2026, 09:21:03 UTC
Last updated: 08/15/2026, 00:41:14 UTC
Views: 88
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.