Skip to content
Web

CVE-2026-72778

8.7
High
EPSS 0.45%Patch availableAug 11, 2026

Authenticated remote code execution in Craft CMS control panel via crafted condition JSON.

common questions

Is CVE-2026-72778 being exploited?

Not confirmed. CVE-2026-72778 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-72778?

CVE-2026-72778 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72778?

Yes. A fix has been recorded for CVE-2026-72778. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72778 affect?

CVE-2026-72778 affects Craft CMS >=4.0.0-RC1 and <4.18.2, Craft CMS >=5.0.0-RC1 and <5.10.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72778?

Upgrade to Craft CMS 4.18.2 or 5.10.6+, restrict control-panel access, rotate creds

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Craft CMS >=4.0.0-RC1 and <4.18.2Craft CMS >=5.0.0-RC1 and <5.10.6
impact

Authenticated attacker with control-panel access and CSRF token can execute OS commands as the PHP/web user via condition.config JSON decoding.

action required

Immediate action required

affected versions
craftcms cms
  • affected>= 5.0.0-RC1 and < 5.10.6
  • affected>= 4.0.0-RC1 and < 4.18.2
vendor says fixed in5.10.6, 4.18.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free