CVE-2026-72781: Craft CMS: Authenticated RCE through Twig sandbox escape

Published Aug 6, 2026
·
Updated

Craft CMS versions >= 5.0.0-RC1 before 5.10.7 and >= 4.0.0-RC1 before 4.18.3 contain a remote code execution vulnerability in the Twig sandbox mechanism. Because Craft marks the ElementInterface as safe (via the AllowedInSandbox attribute) and the sandbox allowlisting extends to the entire class hierarchy (craft\base\Component up to yii\base\Component), an authenticated attacker with permission to access the control panel can render a malicious Twig template that abuses the yii\base\Component arbitrary function-call gadget to execute arbitrary code, even when the Twig sandbox is enabled via enableTwigSandbox().

Other sources

Craft CMS: Authenticated RCE through Twig sandbox escape

— Packagist

The Twig sandbox mechanism in Craft CMS is configured to allow dangerous functionality from the Yii framework, leading to authenticated RCE in a manner similar to previously disclosed vulnerabilities.

The Twig sandbox in Craft CMS works by implementing Twig's SecurityPolicyInterface. The resulting SecurityPolicy class implements the checkMethodAllowed and checkPropertyAllowed methods of the interface. The implementations compare whether the called method or property is in a configured allowlist or is marked with the AllowedInSandbox attribute.

Additionally, SecurityPolicy allows the allowlisting of whole classes, which is shorthand for allowing all methods and properties of that class to be called. Both the allowlists for tags, filters, variables, methods, properties, and classes, as well as the AllowedInSandbox attribute mechanism, are preconfigured by Craft CMS to allow user-defined templates to use core functionality unimpeded. Additionally, Craft CMS project developers can add more to the allowlists or mark their custom methods and so on as safe with AllowedInSandbox.

The SecurityPolicy class's allowlisting mechanism is potentially dangerous, as it allows all methods and properties on an object of the allowed class. This means that the checked object can be a subclass and be allowed. And it means that the allowed methods and properties can be defined on any class of the class hierarchy of the object, which does not have to be the allowed class itself.

Craft CMS uses the AllowedInSandbox attribute to mark the ElementInterface as safe. The Element class implements this interface and is the base class for many relevant model classes in Craft CMS, like Entry, User, Asset and so on. Additionally, Element extends the craft\base\Component class. Going up the class hierarchy of craft\base\Component, eventually the class yii\base\Component is reached, which is located in the Yii framework used by CraftCMS. yii\base\Component is known to contain a dangerous arbitrary function call gadget which leads to previously disclosed RCE vulnerabilities in Craft CMS (GHSA-255j-qw47-wjh5, GHSA-2fph-6v5w-89hh, GHSA-7jx7-3846-m7w7, GHSA-qrgm-p9w5-rrfw). Due to lax class allowlisting, this function-call gadget is allowed in the Twig sandbox. This allows sandboxed Twig templates to use known payloads based on the function-call gadget to achieve RCE.

Impact

An authenticated attacker with permission to access the control panel can render a malicious Twig template and gain RCE, even if the Twig sandbox is enabled through enableTwigSandbox().

— GitHub

Affected Software

6 affected componentsFixes available
Craft CMS Craft CMS>=5.0.0-RC1<5.10.7
Craft CMS Craft CMS>=4.0.0-RC1<4.18.3
composer/craftcms/cms>=4.0.0-RC1, <4.18.3
4.18.3
composer/craftcms/cms>=5.0.0-RC1, <5.10.7
5.10.7
composer/craftcms/cms>=4.0.0-RC1<4.18.3
4.18.3
composer/craftcms/cms>=5.0.0-RC1<5.10.7
5.10.7

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 4.18.3
  2. Upgrade

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

    Fixed in 5.10.7
  3. Upgrade

    Upgrade Craft CMS to a version that resolves this vulnerability.

    Fixed in 5.10.7
  4. Upgrade

    Upgrade Craft CMS to a version that resolves this vulnerability.

    Fixed in 4.18.3

Event History

Aug 6, 2026
Advisory Published
via GitHub·09:02 PM
Data Sourced
via GitHub·09:02 PM
DescriptionWeaknessAffected Software
Data Sourced
via Packagist·09:02 PM
DescriptionSeverityAffected Software
Aug 11, 2026
CVE Published
via MITRE·12:17 PM
Data Sourced
via MITRE·12:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:19 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-72781?

The severity of CVE-2026-72781 is high, with a CVSS score of 8.8.

2

How do I fix CVE-2026-72781?

To fix CVE-2026-72781, update Craft CMS to version 5.10.7 or later, or to version 4.18.3 or later.

3

What type of vulnerability is CVE-2026-72781?

CVE-2026-72781 is a remote code execution vulnerability affecting the Twig sandbox mechanism in Craft CMS.

4

What versions of Craft CMS are affected by CVE-2026-72781?

CVE-2026-72781 affects Craft CMS versions 5.0.0-RC1 through 5.10.6 and 4.0.0-RC1 through 4.18.2.

5

What impact does CVE-2026-72781 have on security?

CVE-2026-72781 allows an attacker to execute arbitrary code on the server via the Twig sandbox escape, potentially compromising the entire system.

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