{"items":[{"id":"NVI-00006110","kind":"vulnerability","title":"Craft CMS: Authenticated RCE via `condition.config` JSON cleanse bypass","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-265m-7826-wjqm","CVE-2026-72778"],"plain_summary":"GitHub lists this reviewed advisory for craftcms/cms, craftcms/cms. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-8d495d5334f418eda3abb4999b2185f5"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.10.6 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.18.2 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-24T15:10:00.190Z","value":"8.8 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-8d495d5334f418eda3abb4999b2185f5"},{"kind":"CVSS","as_of":"2026-10-24T15:10:00.190Z","value":"8.7 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-8d495d5334f418eda3abb4999b2185f5"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0558deeacf660b7a8cf6e797c927be1e","url":"https://github.com/advisories/GHSA-265m-7826-wjqm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-265m-7826-wjqm","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"},{"id":"sr-a7bebf2b6a15214976bd8b241367d450","url":"https://github.com/advisories/GHSA-265m-7826-wjqm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-265m-7826-wjqm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.011Z"},{"id":"sr-8d495d5334f418eda3abb4999b2185f5","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72778","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-72778","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:49.802Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0558deeacf660b7a8cf6e797c927be1e"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":[">= 5.0.0-RC1, < 5.10.6"]},{"certainty":"source_listed","source_ids":["sr-0558deeacf660b7a8cf6e797c927be1e"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":[">= 4.0.0-RC1, < 4.18.2"]},{"certainty":"source_listed","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.10.6"]},{"certainty":"source_listed","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.18.2"]}],"null_published_at":"2026-11-03T17:49:21.368Z","source_updated_at":"2026-09-01T21:07:24.000Z","source_disclosed_at":"2026-08-06T20:45:00.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:40.011Z"},{"id":"NVI-00006110","kind":"vulnerability","title":"Craft CMS: Authenticated RCE via `condition.config` JSON cleanse bypass","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-265m-7826-wjqm","CVE-2026-72778"],"plain_summary":"GitHub lists this reviewed advisory for craftcms/cms, craftcms/cms. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0558deeacf660b7a8cf6e797c927be1e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 5.10.6 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.18.2 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0558deeacf660b7a8cf6e797c927be1e","url":"https://github.com/advisories/GHSA-265m-7826-wjqm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-265m-7826-wjqm","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"},{"id":"sr-a7bebf2b6a15214976bd8b241367d450","url":"https://github.com/advisories/GHSA-265m-7826-wjqm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-265m-7826-wjqm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.011Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0558deeacf660b7a8cf6e797c927be1e"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":[">= 5.0.0-RC1, < 5.10.6"]},{"certainty":"source_listed","source_ids":["sr-0558deeacf660b7a8cf6e797c927be1e"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":[">= 4.0.0-RC1, < 4.18.2"]},{"certainty":"source_listed","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.10.6"]},{"certainty":"source_listed","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.18.2"]}],"null_published_at":"2026-11-02T10:00:37.150Z","source_updated_at":"2026-09-01T21:07:24.000Z","source_disclosed_at":"2026-08-06T20:45:00.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:40.011Z"},{"id":"NVI-00006110","kind":"vulnerability","title":"Craft CMS: Authenticated RCE via `condition.config` JSON cleanse bypass","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-265m-7826-wjqm","CVE-2026-72778"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.10.6 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.18.2 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a7bebf2b6a15214976bd8b241367d450","url":"https://github.com/advisories/GHSA-265m-7826-wjqm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-265m-7826-wjqm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.011Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.10.6"]},{"certainty":"source_listed","source_ids":["sr-a7bebf2b6a15214976bd8b241367d450"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"Craft CMS has an authenticated remote code execution issue in the control panel element-search condition handling.\n\nCraft 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.\n\nBecause `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.\n\nThe 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.\n\n## Preconditions\n\n- The attacker needs an authenticated Craft control panel session.\n- A valid CSRF token is required.\n\n## Impact\n\nAn 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.\n\nPotential atta","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.18.2"]}],"null_published_at":"2026-10-31T22:13:05.859Z","source_updated_at":"2026-09-01T21:15:06.931Z","source_disclosed_at":"2026-08-06T20:45:00.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:40.011Z"}],"next_cursor":null,"snapshot_revision":"42594"}