External risk intelligence

Craft CMS Arbitrary File Write Leading to Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130674

Craft CMS is a content management system typically deployed as an internet-facing web application. Since the vulnerability involves the ability to write files into the web docroot via the application's entry management features, it is commonly accessible to attackers through the public-facing interface of the web server.

Code Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Craft CMS allows unauthorized users to execute arbitrary code on affected systems by crafting specific entry titles. This occurs due to an incomplete fix for how the system handles file creation, enabling attackers to write malicious files directly into the website's accessible directory.

  • Issue: Attackers can write code to servers via content titles.
  • Why remember: It affects public-facing websites and content systems.
  • Takeaway: Confirm if this content system is in use.

Attack Path

How an attacker could exploit the issue

An attacker could start by accessing a Craft CMS installation that is exposed to the internet. By leveraging the ability to create or modify content entries, they could manipulate the title formatting feature. This would allow them to write arbitrary files into the web server's document root, ultimately leading to remote code execution.

  • No authentication or privileges needed.
  • Crafting entry titles triggers file write.
  • Remote code execution.

Live Threat

Current exploitation, exposure, and threat context

An incomplete fix for a known issue allows attackers to write arbitrary files when supported by the entry type title format, potentially leading to remote code execution. This can occur when the non-sandboxed renderer is abused to write controlled content into the web docroot.

  • Server files could be overwritten.
  • Attackers write arbitrary files.
  • Achieve remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Craft CMS impacts the application's ability to securely handle entry title formats, potentially leading to remote code execution. Application owners, in conjunction with infrastructure and security teams, are responsible for assessing and remediating this risk. The first practical step involves identifying all instances of the affected Craft CMS, determining their exposure and criticality, and then coordinating a plan for mitigation, which may include applying vendor-supplied fixes or implementing temporary controls.

  • Craft CMS application owners should lead remediation.
  • Verify affected instances and public exposure.
  • Plan vendor coordination and apply fixes.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Craft CMS and how is it used?

Craft CMS is a flexible content management system (CMS) that developers use to build custom websites and web applications. It serves as the backend platform where users manage digital content, templates, and entry types, which are then rendered and served to visitors via a web server.

What is the vulnerability in CVE-2026-130674?

This CVE involves an improper neutralization of special elements, classified as CWE-94 (Code Injection). It occurs because the system fails to fully block certain inputs. By manipulating entry title formats, an attacker can trick the application into executing code or writing malicious files that the server then processes, leading to remote code execution.

How does an attacker trigger this file write?

An attacker triggers the bug by inputting specific, malicious strings into the entry title format fields. The vulnerability relies on the application's non-sandboxed template renderer to process these titles and write files to the document root. If the entry title format is not configured to use the specific functions associated with the vulnerability, the trigger path is not engaged.

Why is this CVE-2026-130674 relevant to my setup?

According to Halo Surface Signal, Craft CMS is typically deployed as an internet-facing web application. Because this vulnerability allows attackers to write files into the web docroot via public-facing content features, any instance accessible from the internet is at higher risk. Internal-only instances may still be vulnerable if access is not strictly controlled.

What are the first steps to address this issue?

Begin by identifying all running instances of Craft CMS in your environment to determine if they fall within the affected version range. Once identified, evaluate the exposure of these instances to the internet. Prioritize updating the software using vendor-supplied patches, as this is the primary method to resolve the incomplete blocklist fix at its source.

References