External risk intelligence

Craft CMS Remote Code Execution via Class Instantiation

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130675

Craft CMS is a web content management system designed to be public-facing to serve website content. The vulnerability is reachable through public web templates used for payment redirects, placing the attack surface directly on the internet-facing portion of the application.

Remote Code Execution

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 critical vulnerability has been identified in Craft CMS that could allow unauthenticated attackers to execute arbitrary code. This issue arises from how the system processes image transformations, potentially enabling the instantiation of dangerous classes through crafted requests.

  • Code execution flaw in content management system.
  • Affects public-facing websites via payment redirects.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by tricking a user into visiting a crafted URL that utilizes Craft Commerce's payment redirect template. This template, when processing a customer's photo information with a specially manipulated transform, can cause the server to instantiate arbitrary PHP classes. This, in turn, can lead to the execution of arbitrary code on the server.

  • No authentication or privileges needed.
  • Triggered via crafted redirect URL.
  • Allows arbitrary remote code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute arbitrary PHP code on the server by manipulating image transformation parameters. This could occur when a crafted transform is used in a payment redirect template, potentially affecting the integrity and availability of the affected system.

  • Server-side code execution.
  • Via crafted image transformation parameters.
  • Compromise of system integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

The identified remote code execution vulnerability in Craft CMS requires immediate attention from teams responsible for managing web applications and their underlying infrastructure. The initial practical step involves identifying all instances of the affected Craft CMS deployment, assessing their internet-facing exposure and business criticality, and pinpointing the accountable application or platform owner to coordinate remediation efforts.

  • Application or Platform owners should lead remediation.
  • Verify internet-facing exposure and criticality.
  • Plan and execute necessary updates.

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?

Craft CMS is a popular content management system used to build and manage dynamic websites. It functions as the backend engine that powers web pages, handles user data, and manages digital assets like images. Because it is designed to be public-facing to serve content to visitors, it often sits at the edge of a network where it interacts directly with incoming web traffic.

What is the weakness in CVE-2026-130675?

This vulnerability is classified as CWE-697, or insufficient comparison or check. In this specific case, the software fails to properly restrict which classes the system can create when processing image transformations. By supplying specially crafted input, an attacker can trick the application into instantiating unauthorized system classes, which acts as a bridge to execute arbitrary PHP code on the server.

How is this vulnerability triggered?

An attacker triggers the flaw by sending a crafted request that reaches the Craft Commerce payment redirect template. The exploit relies on manipulating specific image transform parameters—specifically by injecting a __class key with a null value—to force the application to instantiate code it should not touch. Simply visiting the site without these specific malicious parameters does not trigger the bug; it requires a targeted, crafted request.

Do I need to worry about this if my site is internal?

Halo Surface Signal classifies this vulnerability as having an external attack surface because Craft CMS is typically deployed as a public-facing web platform. If your instance is exposed to the internet, it is at higher risk because the payment redirect templates are reachable by anyone online. If your instance is strictly internal and unreachable from the internet, the risk is reduced, but you should still review your architecture.

How do I respond to CVE-2026-130675?

The first step is to locate all deployments of Craft CMS within your environment. Prioritize those that are internet-facing or support commerce features, as these are the most accessible paths for an attacker. Identify the platform owners responsible for these systems and coordinate an update to the patched version of the software to eliminate the insecure class instantiation behavior.

References