On this page (7 sections)

A critical remote code execution (RCE) vulnerability, tracked as CVE-2026-130675, affects Craft CMS from 5.0.0 before 5.11.4. According to the GitHub Advisory Database entry, the flaw sits in the image transform code and can be reached through a Craft Commerce template, allowing an attacker to run PHP on the server.

If you run a Craft CMS 5.x site, especially one with Craft Commerce installed, check your version now and plan an update to 5.11.4 or later. The public information is short, so this article sticks to what the advisory states and flags what is still unknown.

What happened

The vulnerability was published on November 18, 2026 in the GitHub Advisory Database and the National Vulnerability Database. The description says Craft CMS contains a remote code execution flaw in ImageTransforms::normalizeTransform(). The NVD entry carries the same text as the GitHub advisory, so it is a repeat of one source rather than independent confirmation.

The GitHub entry is marked as unreviewed and its package fields show affected and patched versions as unknown. The version range (5.0.0 up to, but not including, 5.11.4) comes from the description text itself. A vendor advisory is referenced as GHSA-hq78-cm2m-h24h, but its contents were not available to us, so check it directly for the authoritative fix details.

Technical details

Per the advisory, the problem lets attackers instantiate arbitrary classes by supplying class:null together with a __class key. In plain terms, the code that normalizes image transform settings lets attacker-supplied input influence which PHP class gets created. This is a weakness class often described as unsafe object instantiation: if an attacker can pick the class, they may be able to pick one whose normal behavior has dangerous side effects.

The advisory names yii\rbac\PhpManager as an example of a class that can be instantiated to execute PHP. It also describes a route to the vulnerable method: Craft Commerce's payments/pay redirect template calls customer.photo.getUrl() with a crafted transform. The CWE listed is CWE-697.

The CVSS v4 metrics in the advisory are Attack Vector: Network, Attack Complexity: Low, Attack Requirements: None, Privileges Required: None and User Interaction: None, with High impact on confidentiality, integrity and availability of the vulnerable system. By the score, that means no login and no user action is needed, though the path the advisory describes goes through Craft Commerce. We are deliberately not describing how to build a malicious request.

Who is affected

  • Sites running Craft CMS 5.0.0 through 5.11.3.
  • Sites with Craft Commerce installed, because the advisory says the flaw can be reached through Craft Commerce's payments/pay redirect template. The advisory does not say this is the only route.
  • Sites on Craft 4.x or earlier are outside the stated range, but the research does not say whether those branches are affected or have their own fixes. Confirm with the vendor advisory.

Whether sites without Commerce can be reached by another route is not stated in the research. Treat any 5.x install below 5.11.4 as in scope until the vendor says otherwise.

How to check your exposure

First find the installed Craft version. Run this from your project root on a server with Composer available. It lists the installed craftcms/cms and craftcms/commerce packages and their versions; you are looking for craftcms/cms at 5.11.4 or higher. If Commerce is not installed, Composer will report that package as not found.

Show the installed Craft CMS and Craft Commerce versions (run in the project root)Shell
composer show craftcms/cms craftcms/commerce

You can also see the version in the Craft control panel. To see whether Commerce is in use, check your composer.json and the Plugins page in the control panel.

Next, look at web server logs for requests to the Commerce payment redirect path. This read-only search lists requests that mention it; adjust the log path for your server and web server software. Many hits are normal checkout traffic, so look for odd parameters, unusual sources or errors rather than treating every line as an attack.

Search access logs for requests to the payments/pay path (adjust the log path)Shell
grep -i "payments/pay" /var/log/nginx/access.log

What to do now

  1. Identify every Craft CMS install you manage, including staging and forgotten sites, and record the version of each.
  2. Read the vendor advisory GHSA-hq78-cm2m-h24h for the official fix guidance and any workaround.
  3. Back up the database and files, then update Craft CMS to 5.11.4 or later.
  4. Update Craft Commerce to the latest release compatible with your Craft version.
  5. If you cannot update immediately, restrict access to the site or the checkout path where practical, and consider a web application firewall rule as a temporary layer, not a replacement for the patch.
  6. After updating, review web server logs, recently changed PHP files and the web root for files you do not recognize.
  7. If you find signs of compromise, rotate database credentials, API keys, the Craft security key and admin passwords.

Run the update with Composer from the project root. The command below asks Composer to update Craft CMS to the newest version allowed by your constraints; check that your composer.json permits 5.11.4 or higher.

Caution. Updating changes code and may run database migrations. Take a full backup and test on a staging copy first, and run the update during a low-traffic window if the site takes payments.
Update Craft CMS with Composer (run in the project root, after a backup)Shell
composer update craftcms/cms --with-all-dependencies

After the update, run the version check again and confirm it reports 5.11.4 or later.

Detection and monitoring

Exploitation status is unconfirmed, so do not assume the site is safe just because nothing has been reported. The score describes a network-reachable flaw with low complexity, which is a good reason to patch promptly.

  • Watch for unexpected PHP files in the web root, storage directories and upload folders.
  • Alert on new outbound connections from the web server and on unexpected child processes of PHP-FPM or the web server.
  • Track file integrity on the Craft application directory and on composer.lock.
  • Keep access logs long enough to look back to November 18, 2026, when the issue became public.

An outside-in security scan can help you spot exposed versions and misconfigurations, and monitoring can alert you to certificate, DNS and header changes, but neither replaces patching. For background on what external checks can and cannot see, read what outside-in malware detection can and cannot see. If you suspect a compromise, follow website hacked: what to do.

What is still unknown

  • No exploitation in the wild is reported in the research, and no proof-of-concept is described. Absence of reports is not proof that nobody is exploiting it.
  • The GitHub entry is unreviewed, and only one underlying source exists so far. Details could be refined as the vendor advisory is analyzed.
  • The research does not say whether other Craft branches (such as 4.x) are affected, or whether routes other than Craft Commerce exist.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130675 - GitHub Advisory Databasegithub.com
  2. CVE-2026-130675: Craft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform() that allows attackers to…nvd.nist.gov ·
  • Craft CMS
  • CVE-2026-130675
  • Remote code execution
  • Craft Commerce
  • PHP