craftcms/cms
Affected
- introduced
5.0.0-RC1, fixed5.10.6(ecosystem)
Fixed versions
5.10.6
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-72778
Craft CMS: Authenticated RCE via condition.config JSON cleanse bypass
Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.
Craft cleans the outer request-controlled condition array with Component::cleanseConfig(), but Conditions::createCondition() later decodes and merges the JSON string in condition.config without re-running cleanseConfig() on the decoded/merged configuration.
Because condition.config is a JSON string during the first cleanse, Yii special config keys such as as ... and on ... can be hidden inside it. After JSON decoding, those keys reach FieldLayout object creation and are interpreted by Yii as behavior/event configuration.
The RCE is semi-blind: the trigger endpoint returns a normal JSON response, and the command output is verified via a server-side file-write side effect retrieved in a subsequent request.
Preconditions
Impact
An authenticated control panel user can inject Yii behavior/event configuration after Craft’s intended config cleanse boundary. In the confirmed local lab, this led to command execution as the PHP/web user.
Potential attacker impact:
High Basis: The source's own band: HIGH
5.0.0-RC1, fixed 5.10.6 (ecosystem)5.10.6
The export has no generic command for this ecosystem.
4.0.0-RC1, fixed 4.18.2 (ecosystem)4.18.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0