MediumGHSA-crcq-738g-pqvcCVE-2025-57811

Craft CMS Potential Remote Code Execution via Twig SSTI

Published 25 Aug 2025 · Updated 27 Nov 2025

Affected packages

craftcms/cmsComposer

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

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

craftcms/cmsComposer

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

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

Details

Note that users must have administrator access to the Craft Control Panel, and allowAdminChanges must be enabled for this to work, which is against Craft CMS' recommendations for any non-dev environment.

https://craftcms.com/knowledge-base/securing-craft#set-allowAdminChanges-to-false-in-production

Note: This is a follow-up to GHSA-f3cw-hg6r-chfv

Users should update to the patched versions (4.16.6 and 5.8.7) to mitigate the issue.

Resources: https://github.com/craftcms/cms/pull/17612

Is GHSA-crcq-738g-pqvc 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.