Skip to main content
Menu
CVEs

CVE

Craftcms CMS remote code execution in image transform handling

Affects Craft CMS 5.0.0 before 5.11.4 with Craft Commerce installed. Fixed in Craft CMS 5.11.4.

CVE-2026-130675Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 5.11.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.11.4.

Summary

Craft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform() that allows attackers to instantiate arbitrary classes by supplying class:null with a __class key. Attackers can reach the method through Craft Commerce's payments/pay redirect template calling customer.photo.getUrl() with a crafted transform to instantiate classes like yii\rbac\PhpManager and execute PHP.

Who should check

Teams running Craft CMS 5.x before 5.11.4 with Craft Commerce and public user profile photos

“Craft Commerce renders the signed redirect parameter in payments/pay”

github.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.11.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130675 (Craft CMS 5.0.0 before 5.11.4 RCE via Image Transform Class Guard Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130675 (entry last updated 2026-11-18):
Affected:
- craftcms cms: from 5.0.0, fixed in 5.11.4
Fixed versions: 5.11.4.
Conditions (all must be true for the bug to be hit):
- Craft CMS 5.0.0 before 5.11.4 with Craft Commerce installed, which renders the payments/pay redirect template (source: https://github.com/craftcms/cms/security/advisories/GHSA-hq78-cm2m-h24h)
- A public site user with a profile photo can reach the vulnerable method (source: https://github.com/craftcms/cms/security/advisories/GHSA-hq78-cm2m-h24h)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130675 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130675 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/craftcms/cms/security/advisories/GHSA-hq78-cm2m-h24h
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130675
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130675"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • craftcms cms

    From 5.0.0 · fixed in 5.11.4

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · craftcms/cms · Advisory GHSA-hq78-cm2m-h24h
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130675
RecordNVD · CVE-2026-130675

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130675

Is CVE-2026-130675 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A class guard bypass in Craft CMS's image transform handling can let an unauthenticated remote attacker execute PHP, in the right circumstances.Source: github.com

Which versions are affected by CVE-2026-130675?

cms: from 5.0.0 before 5.11.4.Source: cve.now feed data

Am I affected, and how do I check?

Craft CMS 5.0.0 before 5.11.4 with Craft Commerce installed, where the payments/pay redirect template renders the signed redirect parameter. Public site users with a profile photo can reach the vulnerable method. Check the installed Craft CMS version and whether Craft Commerce is installed.Source: github.com

How do I fix CVE-2026-130675?

Upgrade Craft CMS to 5.11.4 or later.Source: github.com

More CVEs