| Package | Affected versions | Patched versions |
|---|---|---|
| craftcms/cms | ≥ 4.0.0-RC1, < 4.17.8≥ 5.0.0-RC1, < 5.9.14 | 4.17.85.9.14 |
| craft cms | = 4.0.0= 5.0.0> 4.0.0, < 4.17.8> 5.0.0, < 5.9.14 | 4.17.85.9.14 |
Guest users can access Config Sync updater index, obtain signed data, and execute state-changing Config Sync actions (regenerate-yaml, apply-yaml-changes) without authentication.
ConfigSyncController extends BaseUpdaterController, and the base updater is anonymously accessible for control panel requests. index emits signed updater state (data), which can be reused by guests in subsequent requests.
Sensitive actions that are reachable via this method are actionApplyYamlChanges, actionRegenerateYaml, applyExternalChanges, and regenerateExternalConfig.
Guest POST to:
http POST /admin/actions/config-sync/index
Extract data from returned JS state:
Craft.updater = ... setState({"data":"<signedData>", ...});
POST /admin/actions/config-sync/regenerate-yaml
data=<signedData>&<csrfParam>=<csrfToken>
or
POST /admin/actions/config-sync/apply-yaml-changes
data=<signedData>&<csrfParam>=<csrfToken>
Unauthenticated users can execute project configuration sync operations that should be restricted to trusted admin/deployment contexts.
Depending on the pending YAML/config state, this can cause unauthorized config state transitions and a service integrity risk.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free