Act nowDisclosed

Advisory · CVE-2026-130675

Unauthenticated RCE in Craft CMS image transforms

Craft CMS 5 before 5.11.4 lets an unauthenticated attacker reach ImageTransforms::normalizeTransform() and instantiate arbitrary PHP classes, leading to remote code execution.

Vendor
Craft CMS
Product
Craft CMS
Identifier / CWE
CVE-2026-130675
CWE-697
Action timing
Immediate
ELI5

Explain it like I’m five

Craft CMS lets visitors ask for a resized photo, but the resizing instructions can smuggle in a request to build any object the site knows about. An attacker asks for a photo and gets the server to run their code instead.

SIMPLIFIED_ATTACK_PATH04 STEPS
  1. 01Crafted transform

    An attacker supplies a transform with a null class and a __class key through the Craft Commerce payments/pay redirect template calling customer.photo.getUrl().

  2. 02Transform normalized

    ImageTransforms::normalizeTransform() processes the attacker-controlled transform.

  3. 03Arbitrary class instantiated

    The flaw lets the attacker instantiate arbitrary classes, such as the Yii PhpManager RBAC class.

  4. 04Code execution

    With a suitable class instantiated, the attacker executes PHP on the server.

What happened

Craft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform(). Attackers can supply class:null with a __class key and reach the method through Craft Commerce’s payments/pay redirect template calling customer.photo.getUrl() with a crafted transform, instantiating arbitrary classes and executing PHP.

The GitHub security advisory rates it critical at CVSS 9.8. Craft CMS 5.11.4 fixes the flaw.

What to do

  1. Inventory Craft CMS 5 deployments, including sites running Craft Commerce.
  2. Upgrade to Craft CMS 5.11.4 or later using the project release guidance.
  3. Restrict access to the site and the Commerce payments flow while remediation is underway.
  4. Review web and application logs for crafted image transform requests and unexpected class instantiation.
  5. If exploitation is suspected, review the server for persistence and rotate credentials and secrets.

Management note

This is unauthenticated remote code execution in a public CMS with a known trigger path. Patching is the priority, and log review matters because the trigger looks like an ordinary image URL.