Skip to main content
VulnerabilityPublished Updated

CVE-2026-28784: craftcms cms · Template Injection

Affects craftcms cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 5.9.0-beta.1 or 4.17.0-beta.1 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.9.0-beta.1, 4.17.0-beta.1, 5.8.22 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade cms to 5.9.0-beta.1 or 4.17.0-beta.1; craftcms/cms to 5.8.22 or 4.16.18.

Affected software

ProductAffectedFixed in
craftcmscmsAffected
  • >=5.0.0-RC1 <5.9.0-beta.1
Fixed in
  • 5.9.0-beta.1
craftcmscmsAffected
  • >=4.0.0-RC1 <4.17.0-beta.1
Fixed in
  • 4.17.0-beta.1
GitHubcraftcms/cmspkg:github/craftcms/cmsOther threatsAffected
  • <4.16.18
  • <5.8.22
Fixed in
  • 4.16.18
  • 5.8.22

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-28784, organizations should immediately update Craft CMS to versions 5.8.22 or 4.16.18 or later, where the vulnerability is patched. Beyond patching, administrators should disable allowAdminChanges in production environments as recommended by the vendor to reduce the attack surface. Restrict access to the Craft control panel and the System Messages utility to only trusted administrators and limit the number of users with such privileges. Implement strong authentication and authorization controls, including multi-factor authentication for administrative accounts. Regularly audit user permissions and remove unnecessary access rights. Monitor logs for unusual Twig input or attempts to access the System Messages utility. Employ web application firewalls (WAFs) with rules to detect and block suspicious template injection patterns. Conduct regular security assessments and penetration tests focusing on CMS components. Finally, maintain a robust backup and incident response plan to recover quickly in case of compromise.

Description

Craft is a content management system (CMS). Prior to 5.8.22 and 4.16.18, it is possible to craft a malicious payload using the Twig map filter in text fields that accept Twig input under Settings in the Craft control panel or using the System Messages utility, which could lead to a RCE. For this to work, you must have administrator access to the Craft Control Panel, and allowAdminChanges must be enabled for this to work, which is against our recommendations for any non-dev environment. Alternatively, you can have a non-administrator account with allowAdminChanges disabled, but you have access to the System Messages utility. Users should update to the patched versions (5.8.22 and 4.16.18) to mitigate the issue.

References

Community reviews

Loading reviews…