craftcms/cms
Affected
- introduced
5.0.0-RC1, fixed5.9.14(ecosystem)
Fixed versions
5.9.14
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-33159
Craft CMS: Unauthenticated Users Can Perform Restricted Project Config Sync Operations
Summary
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.
Details
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.
Reproduction steps
http POST /admin/actions/config-sync/index
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>
Impact
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.
Resources
https://github.com/craftcms/cms/commit/7f0ead833f7
Medium Basis: The source's own band: MODERATE
5.0.0-RC1, fixed 5.9.14 (ecosystem)5.9.14
The export has no generic command for this ecosystem.
4.0.0-RC1, fixed 4.17.8 (ecosystem)4.17.8
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