Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs
Published 1 Mar 2026 · Updated 25 Mar 2026
Affected packages
- Affected
- <5.73.16
- Fixed in
- 5.73.16
composer require statamic/cms:^5.73.16- Affected
- >=6.0.0-alpha.1 <6.7.2
- Fixed in
- 6.7.2
composer require statamic/cms:^6.7.2Details
Impact
An authenticated control panel user with access to Antlers-enabled inputs may be able to achieve remote code execution in the application context. That can lead to full compromise of the application, including access to sensitive configuration, modification or exfiltration of data, and potential impact on availability.
Exploitation is only possible where Antlers runs on user-controlled content—for example, content fields with Antlers explicitly enabled (requiring permission to configure fields and to edit entries), built-in config that supports Antlers such as Forms email notification settings (requiring configuration permission), or third-party addons that add Antlers-enabled fields to entries (for example, the SEO Pro addon). In each case the attacker must have the relevant control panel permissions.
Patches
This has been fixed in 5.73.16 and 6.7.2.
Note that a follow-up report showed that the original 5.73.11 & 6.4.0 fixes were insufficient.
If you use addons that depend on Statamic, ensure that after updating you are running a patched Statamic version.
Is GHSA-cpv7-q2wx-m8rw 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 statamic/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.