Security alerts · November 18, 2026

Critical Craft CMS 5 flaw could let attackers run their own code on the server

Craft CMS versions 5.0.0 up to (but not including) 5.11.4 contain a flaw that, under the right circumstances, lets an unauthenticated attacker run their own PHP code on the server. The vendor describes an attack path through the Craft Commerce plugin. Version 5.11.4 fixes it.

What happened

On November 2, 2026, the developers of the Craft CMS content management system published a security advisory on GitHub, tracked as GHSA-hq78-cm2m-h24h. The bug sits in the part of the system that handles image transforms, such as resizing or cropping photos on a website. Because of a faulty check, an attacker can, under certain circumstances, slip past a safeguard and make the server run PHP code of their choosing.

The issue was reported by a security researcher going by the name 0xkalawy. It was added to the US National Vulnerability Database (NVD) on November 18, 2026 as CVE-2026-130675. In the European vulnerability database EUVD, run by ENISA, it is listed as EUVD-2026-128749.

Nobody has confirmed active exploitation so far: the flaw is not in the CISA KEV catalog and EUVD does not list it as exploited. Still, the technical write-up has been public since early November, so there is no reason to put off the update.

Why it is dangerous

This is an “incorrect comparison” bug (CWE-697). Picture a receptionist who is supposed to send every visitor to the meeting room and only checks whether someone’s invitation names a different room. The check has a blind spot, so a visitor with a slightly differently filled-in invitation can walk wherever they like. In Craft CMS, this lets an attacker hand the system something entirely different from a normal image transform object, which according to the vendor can end with PHP code being executed.

The vendor states that an unauthenticated remote attacker can execute PHP “in the right circumstances.” The described path goes through the payment page of the Craft Commerce e-shop plugin and involves a public site user’s profile photo. The attack works over the internet and does not require access to the control panel.

If it succeeds, the attacker can run code with the web application’s privileges. That could let them read and change the database with customers and orders, steal passwords and keys from the configuration (for example payment gateway credentials), or tamper with page content. If the server sits inside a company network, it could also be used as a stepping stone.

CVSS is an international severity scale from 0 to 10. This flaw scores 9.8 (CVSS 3.1), which is critical. The score was assigned by VulnCheck, not by NVD itself. The vendor rates the issue as “High” on GitHub without a numeric score. The CISA KEV catalog lists vulnerabilities that the US agency CISA has seen exploited in the wild. This one is not in it so far.

Who is affected

Craft CMS is a content management system written in PHP, popular with web agencies for company websites, brochure sites and online shops. It usually runs on Linux servers, VPS instances or standard shared hosting with PHP and a database.

  • Affected: Craft CMS from 5.0.0 up to (but not including) 5.11.4.
  • Highest risk: sites running the Craft Commerce plugin, because the attack path described by the vendor goes through its payment page.
  • Not affected: Craft CMS 5.11.4 and later. The vendor does not list the older major versions (Craft 4 and 3) as affected.

Even if you don’t use Commerce, update anyway. The flawed code lives in the Craft CMS core, and the vendor lists every version from 5.0.0 up to 5.11.4 as vulnerable, not just sites with Commerce. If an agency runs your site, ask them directly which version you are on.

How to check if you are affected

The easiest way is the Craft CMS control panel: under Utilities → System Report you will see the Craft CMS version and the list of installed plugins, including Craft Commerce. Plugins are also listed under Settings → Plugins.

If you have SSH access to the server, go to the project folder (where composer.json lives) and run the commands below. They only read information and change nothing.

composer show craftcms/cms
composer show craftcms/commerce
grep -A 1 '"name": "craftcms/cms"' composer.lock

If your 5.x version is lower than 5.11.4, you are affected. If the second command reports that the package was not found, you are not using Commerce.

How to fix it

The bug is fixed in Craft CMS 5.11.4. The vendor does not offer a temporary workaround, so updating is the only reliable protection. Recommended steps:

  • Back up the database and the site files.
  • If you have a staging copy of the site, test the update there first.
  • Update Craft CMS to 5.11.4 or later, either in the control panel under Utilities → Updates or with Composer using the commands below.
  • After updating, check the version again as described in the previous section and make sure the site and orders work.
composer require craftcms/cms:^5.11.4 -W
php craft up

Order of work: public sites running Craft Commerce first, then all other Craft CMS 5 sites. If you cannot update right away, agree with whoever runs the site on temporarily restricting access to the payment pages. Note that this is not an official vendor recommendation, only a stopgap.

What if you may already be compromised

Neither the vendor nor NVD has published specific indicators of compromise. If you ran a vulnerable version, especially with Craft Commerce, it is worth checking:

  • web server access logs since early November 2026, particularly unusually long or odd requests to the Commerce payment page (payments/pay),
  • new or modified PHP files in the web/ and storage/ folders that you did not put there,
  • unknown admin accounts or changed permissions under Users,
  • errors in storage/logs/, unfamiliar cron jobs and unexpected outbound connections from the server.

The command below also searches older compressed logs. The paths are typical for nginx and Apache on Debian and Ubuntu, so adjust them to match your server.

zgrep -iE 'payments(/|%2F)pay' /var/log/nginx/access.log* /var/log/apache2/access.log* 2>/dev/null

Run the next command in the project folder. It lists PHP files changed in the last 30 days. Craft also stores its own compiled templates in storage/runtime/, so focus on files with unfamiliar names.

find web storage -name "*.php" -mtime -30

If you find anything suspicious, don’t delete it and keep copies of the logs. Bring in an incident response specialist, and after cleanup rotate the database passwords and the keys in .env, including payment gateway credentials. If customer personal data may have leaked, GDPR may require you to notify your data protection authority within 72 hours.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.