cve.bz

CVE-2026-72778 craftcms cms

8.7 highEPSS 0.8%Fix available

High (8.7) in craftcms cms. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in craftcms/cms 4.18.2, 5.10.6.

On this page
Craft CMS versions from 4.0.0-RC1 before 4.18.2 and from 5.0.0-RC1 before 5.10.6 contain an authenticated remote code execution vulnerability in the control panel element-search condition handling. Craft cleanses the outer request-controlled condition array via Component::cleanseConfig(), but Conditions::createCondition() later decodes and merges the JSON string in condition.config without re-running cleanseConfig() on the decoded configuration. Because condition.config is a JSON string during the first cleanse, Yii special config keys such as 'as ...' and 'on ...' can be hidden inside it and, after JSON decoding, are interpreted by Yii as behavior/event configuration during FieldLayout object creation. An attacker with an authenticated control panel session (and a valid CSRF token) can exploit this to execute operating system commands as the PHP/web user.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • craftcms/cms (Packagist): fixed in 5.10.6, 4.18.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-72778 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72778?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72778?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72778 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
craftcms cmsfrom 5.0.0-RC1 before 5.10.6
craftcms cmsfrom 4.0.0-RC1 before 4.18.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-265m-7826-wjqmPackagistcraftcms/cms>=5.0.0-RC1 <5.10.65.10.6
GHSA-265m-7826-wjqmPackagistcraftcms/cms>=4.0.0-RC1 <4.18.24.18.2

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON