Skip to main content
VulnerabilityPublished

CVE-2026-55794: craftcms cms · Template Injection

Affects craftcms cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 5.10.0 soon.

Data as of 13 Nov 2026, 23:54 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.10.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 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 13 Nov 2026.

What to do

Upgrade cms and craftcms/cms to 5.10.0.

Affected software

ProductAffectedFixed in
craftcmscmsAffected
  • >=5.9.0 <5.10.0
Fixed in
  • 5.10.0
GitHubcraftcms/cmspkg:github/craftcms/cmsOther threatsAffected
  • >=5.9.0 <5.10.0
Fixed in
  • 5.10.0

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

AI-suggested

Upgrade Craft CMS to version 5.10.0 or later, where this vulnerability is fixed by using sandboxed template rendering for the signed redirect URL. Patch status is not explicitly stated beyond the fix in 5.10.0, so users should apply this official update promptly.

Description

Craft CMS is a content management system (CMS). In versions 5.9.0 and above prior to 5.10.0, control panel users with the ability to edit entries can execute unsandboxed Twig code via the HTTP Referrer header, potentially leading to authenticated RCE. 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 issue has been fixed in version 5.10.0.

References

Community reviews

Loading reviews…