Is CVE-2026-44011 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44011 being exploited in the wild.

How severe is CVE-2026-44011?

High severity, with a CVSS score of 4, published 12 May 2026.

Which products and versions are affected?

craftcms/cms (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.17.12.

Is there a fix for CVE-2026-44011?

Yes. craftcms/cms (Packagist): upgrade to 4.17.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44011 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44011?

Check whether you run craftcms/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44011: Craft CMS authenticated remote code execution in FieldLayout

CVE-2026-44011 · Severity: high · CVSS 4 · Published 2026-05-12

Craft CMS is a content management system used to build and manage websites. A security flaw allows an authorized user to inject malicious settings into the system's configuration. This can lead to remote code execution, allowing an attacker to take full control of the server, access sensitive data, or disrupt operations.

Technologies: craftcms/cms (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-44011 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44011 being exploited in the wild.
How severe is CVE-2026-44011?: High severity, with a CVSS score of 4, published 12 May 2026.
Which products and versions are affected?: craftcms/cms (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.17.12.
Is there a fix for CVE-2026-44011?: Yes. craftcms/cms (Packagist): upgrade to 4.17.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44011 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44011?: Check whether you run craftcms/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

craftcms/cms (Packagist): upgrade to 4.17.12 or later
```
composer require craftcms/cms:^4.17.12
```

Technical details

Craft CMS contains a vulnerability in the Yii object creation path where request-controlled condition field layout data is converted into a FieldLayout object without proper cleansing via Component::cleanseConfig(). Because Craft configures models before the parent constructor is called, an attacker can inject special configuration keys that take effect during object creation. Specifically, an authenticated attacker can issue a crafted POST request to endpoints like /admin/actions/element-search/search to attach a malicious behavior (e.g., yii\behaviors\AttributeTypecastBehavior) and trigger a same-request event that executes arbitrary system commands. This is a variant of behavior-injection vulnerabilities and is fixed in versions 4.17.12 and 5.9.18.

Affected products

Craft CMS Craft CMS 4.0.0 to 4.17.11, 5.0.0 to 5.9.17

Identifiers

CVE-2026-44011
GHSA-qrgm-p9w5-rrfw

Timeline

2026-04-27: advisory: Vendor advisory GHSA-qrgm-p9w5-rrfw published
2026-05-12: disclosed: CVE-2026-44011 published
2026-05-12: patched: Fixes released in versions 4.17.12 and 5.9.18

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.