Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-28695: CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine in craftcms cms

0
High
VulnerabilityCVE-2026-28695cvecve-2026-28695cwe-1336
Published: Wed Mar 04 2026 (03/04/2026, 16:15:32 UTC)
Source: CVE Database V5
Vendor/Project: craftcms
Product: cms

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.

AI-Powered Analysis

AILast updated: 03/04/2026, 16:48:35 UTC

Technical Analysis

CVE-2026-28695 is a critical security vulnerability affecting Craft CMS, a popular content management system. The issue is a server-side template injection (SSTI) vulnerability that enables authenticated administrators to achieve remote code execution (RCE). The root cause lies in the improper neutralization of special elements in the Twig template engine's create() function, which exposes the Craft::createObject() method. This method allows instantiation of arbitrary PHP classes with constructor arguments. Attackers can exploit this by chaining with the symfony/process dependency bundled within Craft CMS, enabling execution of arbitrary system commands on the server. This vulnerability effectively bypasses the prior patch for CVE-2025-57811, indicating a regression or incomplete fix. The affected versions include Craft CMS from 5.8.7 up to but not including 5.9.0-beta.1, and from 4.0.0-RC1 up to but not including 4.17.0-beta.1. The vulnerability requires authenticated admin privileges but does not require user interaction, and it has a CVSS 4.0 score of 7.5, reflecting high severity. No public exploits have been reported yet, but the potential for damage is significant due to the ability to execute arbitrary code on the server. The issue is addressed in versions 5.9.0-beta.1 and 4.17.0-beta.1, where the create() function's exposure has been properly mitigated.

Potential Impact

The impact of CVE-2026-28695 is substantial for organizations using vulnerable versions of Craft CMS. Successful exploitation allows an authenticated administrator to execute arbitrary code on the underlying server, potentially leading to full system compromise. This can result in unauthorized data access, data modification or destruction, deployment of malware or ransomware, and lateral movement within the network. Since Craft CMS is often used to manage websites and web applications, attackers could deface sites, steal sensitive user data, or use the compromised server as a pivot point for further attacks. The vulnerability bypasses previous patches, indicating that organizations relying on earlier fixes remain at risk. The requirement for admin authentication limits exposure to some extent, but insider threats or compromised admin credentials could be leveraged by attackers. The absence of known exploits in the wild suggests a window of opportunity for defenders to patch before widespread attacks occur.

Mitigation Recommendations

To mitigate CVE-2026-28695, organizations should immediately upgrade Craft CMS installations to version 5.9.0-beta.1 or later, or 4.17.0-beta.1 or later, where the vulnerability is fixed. Administrators should audit and restrict admin access to trusted personnel only, enforce strong authentication mechanisms such as multi-factor authentication (MFA), and monitor admin activities for suspicious behavior. It is also advisable to review and limit the use of custom Twig templates that invoke the create() function or other dynamic object instantiations. Network segmentation and application-layer firewalls can help reduce exposure of the CMS backend. Regularly scanning for outdated CMS versions and applying security patches promptly is critical. Additionally, monitoring logs for unusual process executions or command invocations related to symfony/process can provide early detection of exploitation attempts. Finally, consider implementing runtime application self-protection (RASP) or web application firewalls (WAFs) with rules targeting SSTI patterns to provide an additional layer of defense.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-02T21:43:19.928Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69a85ed1d1a09e29cb4aedf1

Added to database: 3/4/2026, 4:33:21 PM

Last enriched: 3/4/2026, 4:48:35 PM

Last updated: 3/4/2026, 6:04:21 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses