Skip to main content
VulnerabilityPublished Updated

CVE-2026-28695: craftcms cms · Template Injection

Affects craftcms cmsSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 7.5 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
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% 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
CVSS:4.0/AV:N/AC:L/AT:P/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: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade craftcms cms to 5.9.0-beta.1 or 4.17.0-beta.1.

Affected software

ProductAffectedFixed in
craftcmscmsAffected
  • >=5.8.7 <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
  • =5.9.0-beta.1
  • =4.17.0-beta.1
Fixed in–

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

AI-suggested

Organizations should immediately upgrade Craft CMS to versions 5.9.0-beta.1 or later, or 4.17.0-beta.1 or later, where the vulnerability is patched. Until upgrades can be applied, restrict admin access to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. Review and monitor admin account activity for suspicious behavior. Disable or restrict access to the Twig create() function or Craft::createObject() if possible through configuration or custom code hardening. Employ web application firewalls (WAFs) with rules designed to detect and block unusual template engine usage or command injection patterns. Conduct thorough code and configuration audits to ensure no other template injection vectors exist. Regularly back up CMS data and system configurations to enable recovery in case of compromise. Finally, maintain vigilant monitoring of security advisories for any emerging exploits or related vulnerabilities.

Description

Craft is a content management system (CMS). There is an authenticated admin RCE in Craft CMS 5.8.21 via Server-Side Template Injection using the create() Twig function combined with a Symfony Process gadget chain. The create() Twig function exposes Craft::createObject(), which allows instantiation of arbitrary PHP classes with constructor arguments. Combined with the bundled symfony/process dependency, this enables RCE. This bypasses the fix implemented for CVE-2025-57811 (patched in 5.8.7). This vulnerability is fixed in 5.9.0-beta.1 and 4.17.0-beta.1.

References

Community reviews

Loading reviews…