CVE-2026-33159: Craft CMS: Unauthenticated users could execute project configuration sync operations that should be restricted trusted users

Published Mar 24, 2026
·
Updated

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

1. Guest POST to:

http POST /admin/actions/config-sync/index

2. Extract data from returned JS state:

Craft.updater = ... setState({"data":"<signedData>", ...});

3. Reuse data as a guest:

POST /admin/actions/config-sync/regenerate-yaml data=<signedData>&<csrfParam>=<csrfToken>

or

POST /admin/actions/config-sync/apply-yaml-changes data=<signedData>&<csrfParam>=<csrfToken>

4. Observe completed response and state/file changes.

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

Other sources

Craft CMS is a content management system (CMS). From version 4.0.0-RC1 to before version 4.17.8 and from version 5.0.0-RC1 to before version 5.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. This issue has been patched in versions 4.17.8 and 5.9.14.

MITRE

Affected Software

10 affected componentsFixes available
composer/craftcms/cms>=4.0.0-RC1<=4.17.7
4.17.8
composer/craftcms/cms>=5.0.0-RC1<=5.9.13
5.9.14
CraftCMS Craft CMS>4.0.0<4.17.8
CraftCMS Craft CMS>5.0.0<5.9.14
CraftCMS Craft CMS=4.0.0
CraftCMS Craft CMS=4.0.0-rc1
CraftCMS Craft CMS=4.0.0-rc2
CraftCMS Craft CMS=4.0.0-rc3
CraftCMS Craft CMS=5.0.0
CraftCMS Craft CMS=5.0.0-rc1

Event History

Mar 24, 2026
Advisory Published
via GitHub·04:57 PM
Data Sourced
via GitHub·04:57 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·05:28 PM
Data Sourced
via MITRE·05:28 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33159?

CVE-2026-33159 has a high severity rating due to the potential for unauthenticated users to perform critical configuration changes.

2

How do I fix CVE-2026-33159?

To fix CVE-2026-33159, upgrade Craft CMS to version 4.17.8 or 5.9.14.

3

What operations are affected by CVE-2026-33159?

CVE-2026-33159 allows unauthenticated users to execute project configuration sync operations, such as regenerating YAML and applying YAML changes.

4

Which versions of Craft CMS are vulnerable to CVE-2026-33159?

Craft CMS versions 4.0.0-RC1 to 4.17.7 and 5.0.0-RC1 to 5.9.13 are vulnerable to CVE-2026-33159.

5

Who can exploit CVE-2026-33159?

CVE-2026-33159 can be exploited by guest users who are not authenticated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203