HighGHSA-x684-96hh-833xCVE-2025-23209

Craft CMS has a potential RCE with a compromised security key

Published 21 Jan 2025 · Updated 22 Oct 2025

Affected packages

craftcms/cmsComposer

Affected: >=5.0.0-RC1 <5.5.8
Fixed in: 5.5.8

Update to the fixed version for your release line, for example:composer require craftcms/cms:^5.5.8

craftcms/cmsComposer

Affected: >=4.0.0-RC1 <4.13.8
Fixed in: 4.13.8

Update to the fixed version for your release line, for example:composer require craftcms/cms:^4.13.8

Details

Impact

This is an RCE vulnerability that affects Craft 4 and 5 installs where your security key has already been compromised.

https://craftcms.com/knowledge-base/securing-craft#keep-your-secrets-secret

Anyone running an unpatched version of Craft with a compromised security key is affected.

Patches

This has been patched in Craft 5.5.8 and 4.13.8.

Workarounds

If you can't update to a patched version, then rotating your security key and ensuring its privacy will help to migitgate the issue.

References

https://github.com/craftcms/cms/commit/e59e22b30c9dd39e5e2c7fe02c147bcbd004e603

Is GHSA-x684-96hh-833x in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected craftcms/cms, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.