MediumGHSA-j5g9-j7r4-6qvxCVE-2024-21622

Craft CMS Privilege Escalation

Published 3 Jan 2024 · Updated 10 Sept 2026

Affected packages

craftcms/cmsComposer
Affected
>=4.0.0-RC1 <4.5.11
Fixed in
4.5.11
Update to the fixed version for your release line, for example:composer require craftcms/cms:^4.5.11
craftcms/cmsComposer
Affected
>=3.0.0 <3.9.6
Fixed in
3.9.6
Update to the fixed version for your release line, for example:composer require craftcms/cms:^3.9.6

Details

Impact

This is a potential moderate impact, low complexity privilege escalation vulnerability in Craft with certain user permissions setups.

Patches

This has been fixed in Craft 4.4.16 and Craft 3.9.6. Users should ensure they are running at least those versions.

References

https://github.com/craftcms/cms/pull/13932 https://github.com/craftcms/cms/pull/13931 https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#4511---2023-11-16 https://github.com/craftcms/cms/blob/v3/CHANGELOG.md#396---2023-11-16

Is GHSA-j5g9-j7r4-6qvx 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.

References

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