Craft CMS: Potential authenticated Remote Code Execution via referrer redirect
Published 6 Jul 2026 · Updated 10 Sept 2026
Affected package
- Affected
- >=5.9.0 <5.10.0
- Fixed in
- 5.10.0
composer require craftcms/cms:^5.10.0Details
Requirements:
- Control panel access
- Permissions to edit an entry
Details
Control panel users with the ability to edit entries can execute unsandboxed Twig code via the HTTP Referrer header.
The issue happens when a user is saving entries. Strings for a signed redirect URL are being compiled as a Twig template via renderObjectTemplate(), and while a sandboxed alternative already exists (renderSandboxedObjectTemplate()), it is not used in this case. This signed URL can be specified by users, as it is reflected in the “Referer” HTTP request header, which is under attacker control.
This has been fixed in Craft 5.10.0. Affected users should update to that version or higher to get the fix.
Resources
https://github.com/craftcms/cms/pull/18680
Is GHSA-f74w-488g-8x5r 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.