GHSA-f5wm-88jv-g5hx

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` i