CVE-2026-72781: Craft CMS Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-f5wm-88jv-g5hx
CWE-693
Published
Advisory Summary

CVE-2026-72781 is a HIGH remote code execution vulnerability (CWE-693: Protection Mechanism Failure) affecting Craft CMS libraries in the Packagist ecosystem. The issue involves authenticated rce through twig sandbox escape. Remediation is available by upgrading affected packages to version 5.10.7, 4.18.3.

CVE-2026-72781 at a Glance

CVE Identifier CVE-2026-72781
GHSA Identifier GHSA-f5wm-88jv-g5hx
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-693: Protection Mechanism Failure
Affected Product Craft CMS
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-72781

To remediate this vulnerability, upgrade all affected Craft CMS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

craftcms/cms fixed: 5.10.7
Upgrade craftcms/cms to 5.10.7
craftcms/cms fixed: 4.18.3
Upgrade craftcms/cms to 4.18.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for craftcms/cms

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-72781, inspect your project dependencies for Craft CMS:

inspect dependencies for craftcms/cms

Analyze the terminal output to locate any version of Craft CMS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.10.7), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-693: Protection Mechanism Failure, where the product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. In Craft CMS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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()`.

CVE-2026-72781 Affected Craft CMS Versions

2 component(s)
Fixed Versions:
5.10.74.18.3
Product / Package Ecosystem Affected Versions Fixed Version
craftcms/cms
Packagist
≥ 5.0.0-RC1
< 5.10.7
5.10.7
craftcms/cms
Packagist
≥ 4.0.0-RC1
< 4.18.3
4.18.3

References

Frequently Asked Questions

What is CVE-2026-72781?
CVE-2026-72781 is a security vulnerability in Craft CMS involving Authenticated RCE through Twig sandbox escape under CWE-693: Protection Mechanism Failure.
Which Craft CMS versions are affected?
Affected versions include releases prior to 5.10.7, 4.18.3 across affected packages: craftcms/cms.
What version fixes CVE-2026-72781?
Upgrading to 5.10.7, 4.18.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is craftcms/cms affected?
Yes, craftcms/cms is affected in releases prior to 5.10.7, 4.18.3. Upgrade your dependency to 5.10.7, 4.18.3 or later.
What CWE is associated with CVE-2026-72781?
CVE-2026-72781 is classified under CWE-693: Protection Mechanism Failure (The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.).
How can I check Packagist dependencies for CVE-2026-72781?
Run the dependency tree command: 'inspect dependencies for craftcms/cms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f5wm-88jv-g5hx",
  "modified" : "2026-09-01T21:04:12Z",
  "published" : "2026-08-06T21:02:28Z",
  "aliases" : [ "CVE-2026-72781" ],
  "summary" : "Craft CMS: Authenticated RCE through Twig sandbox escape",
  "details" : "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.\n\nThe 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.\n\nAdditionally, `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`.\n\nThe `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.\n\n\nCraft 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.\n\n## Impact\n\nAn 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()`.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "craftcms/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0-RC1"
      }, {
        "fixed" : "5.10.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "craftcms/cms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0-RC1"
      }, {
        "fixed" : "4.18.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/craftcms/cms/security/advisories/GHSA-f5wm-88jv-g5hx"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72781"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/craftcms/cms/commit/0b8be1556be4e030578ec779c3e17ffe2e69d7db"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/craftcms/cms"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/craftcms/cms/releases/tag/4.18.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/craftcms/cms/releases/tag/5.10.7"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/craft-cms-rc1-before-remote-code-execution-via-twig-sandbox-escape"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-693" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-06T21:02:28Z",
    "nvd_published_at" : null
  }
}