CVE-2026-55792: Craft CMS: Sensitive File Disclosure / Server-Side File Read

Published Jul 1, 2026
·
Updated

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, CRAFTSECURITYKEY, and third-party API keys, passes all of Craft’s existing dataUrl() protection checks and is fully exfiltrated. Obtaining CRAFTSECURITYKEY 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.

Other sources

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, CRAFTSECURITYKEY, and third-party API keys, passes all of Craft’s existing dataUrl() protection checks and is fully exfiltrated. Obtaining CRAFTSECURITYKEY enables an attacker to forge session tokens and escalate to full admin account takeover.

Details Affected versions: Craft CMS 4.x, 5.x (confirmed against 5.9.19)

The vulnerability arises from the combination of three code facts: 1. dataUrl is in the Twig sandbox allowlist src/config/twig-sandbox.php, line 115: php'allowedFunctions' => [ ... 'dataUrl', // ← allows file reading inside sandboxed templates ... ],

2. Html::dataUrl() does not block dotfiles src/helpers/Html.php, lines 1065–1090. The function applies four checks before reading a file:

Must be within the project root .env is at the root Must not be in a system directory (config/, vendor/, storage/, templates/) .env is not Must not be a .php file .env has no extension File must exist .env always exists in a Craft install

There is no check for dotfiles or specifically for .env. All four checks pass silently and filegetcontents() is called, with the result returned as data:text/plain;base64,....

3. System message body is rendered via renderSandboxedString() src/mail/Mailer.php, lines 181–183: php$subject = $view->renderSandboxedString($systemMessage->subject, $variables); $textBody = $view->renderSandboxedString($systemMessage->body, $variables); $htmlBody = $view->renderSandboxedString($systemMessage->body, $variables, escapeHtml: true);

Any body content saved to a system message is executed inside the Twig sandbox when the email renders. Because dataUrl is in allowedFunctions, the sandbox policy permits its execution without restriction.

Access control: The utility:system-messages permission is a non-admin CP permission grantable to any user group via Settings > Users > Groups. It is not restricted to admins.

Impact Vulnerability type: Sensitive File Disclosure / Server-Side File Read Who is impacted: Any Craft CMS 4.x or 5.x installation where at least one non-admin control panel user has been granted the utility:system-messages permission, and email sending is configured.

Resources:

- https://github.com/craftcms/cms/pull/18559

GitHub

Affected Software

3 affected componentsFixes available
Craft CMS Craft CMS>4.0.0-RC1<=4.18.0, >5.0.0-RC1<5.10.0
composer/craftcms/cms>=5.0.0-RC1<5.10.0
5.10.0
composer/craftcms/cms>=4.0.0-RC1<4.18.0
4.18.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/craftcms/cms to a version that resolves this vulnerability.

    Fixed in 5.10.0
  2. Upgrade

    Upgrade composer/craftcms/cms to a version that resolves this vulnerability.

    Fixed in 4.18.0
  3. Upgrade

    Upgrade Craft CMS to a version that resolves this vulnerability.

    Fixed in 4.18.0
  4. Upgrade

    Upgrade Craft CMS to a version that resolves this vulnerability.

    Fixed in 5.10.0
  5. Compensating control

    Restrict the non-admin CP permission 'utility:system-messages' (Settings > Users > Groups) so that only trusted groups can send/edit system messages, since any user with this permission can embed a file-reading payload in system email templates via the Twig sandbox dataUrl() function.

Event History

Jul 1, 2026
CVE Published
via MITRE·11:20 PM
Data Sourced
via MITRE·11:20 PM
DescriptionWeakness
Jul 2, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeakness
Jul 6, 2026
Advisory Published
via GitHub·09:29 PM
Data Sourced
via GitHub·09:29 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-55792?

The severity of CVE-2026-55792 is rated medium with a CVSS score of 6.

2

How do I fix CVE-2026-55792?

To mitigate CVE-2026-55792, upgrade Craft CMS to version 4.18.0 or 5.10.0 and above.

3

What is the risk associated with CVE-2026-55792?

CVE-2026-55792 poses a risk of sensitive file disclosure and server-side file read through the dataUrl() Twig function.

4

Which versions of Craft CMS are affected by CVE-2026-55792?

Craft CMS versions starting from 4.0.0-RC1 up to 4.18.0 and 5.0.0-RC1 up to 5.10.0 are affected by CVE-2026-55792.

5

What type of vulnerability is CVE-2026-55792 categorized as?

CVE-2026-55792 is categorized as an information leakage vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203