Craft CMS 5.10.0 before 5.11.2 RCE via app/render-elements Signing Oracle
Craft CMS 5.10.0 before 5.11.2 is affected when the app/render-elements request uses hyperlink=true, a non-modal context, and a templated returnUrl. Fixed in 5.11.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.11.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Craft CMS version 5.10.0 up to but not including 5.11.2 The app/render-elements request uses hyperlink=true, a non-modal context, and a templated returnUrl
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Affected releases of Craft CMS contain a remote code execution flaw that lets a non-administrator control panel user run operating system commands as the PHP worker. The attack is carried out remotely over the network, requires a low-privilege login but no user interaction, and abuses the app/render-elements endpoint.
Read the original description
Craft CMS from 5.10.0 before 5.11.2 contains a remote code execution vulnerability that allows non-administrator control panel users to obtain HMAC-signed Twig templates via the app/render-elements endpoint. Attackers can submit the signed templated returnUrl as the login redirect parameter, triggering unsandboxed renderObjectTemplate() evaluation and executing OS commands as the PHP worker.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Craft CMS version 5.10.0 up to but not including 5.11.2 The app/render-elements request uses hyperlink=true, a non-modal context, and a templated returnUrlUpgrade to a fixed version: 5.11.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- craftcms cms
From 5.10.0 · fixed in 5.11.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124430
Is CVE-2026-124430 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets a control panel user run arbitrary operating system commands as the PHP/web-server worker. That process can read the Craft security key, database, environment credentials, CMS content, and other files it can access.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124430?
cms: from 5.10.0 before 5.11.2.Source: cve.now feed data
Am I affected, and how do I check?
Craft CMS from 5.10.0 up to but not including 5.11.2 is affected. The exposed setup is an app/render-elements request that uses hyperlink=true, a non-modal context, and a templated returnUrl. Check the installed Craft version in composer.lock to see whether the version range applies.Source: vulncheck.com, github.com
How do I fix CVE-2026-124430?
Upgrade Craft CMS to 5.11.2 or later. The facts list no workaround.Source: vulncheck.com, github.com