Craft CMS 5.0.0 before 5.11.2 Privilege Escalation via Public Registration
- Exploited
- No known exploitation
- Fix
- Fixed in 5.11.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.11.2.
- 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? →
- 26/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? →
- Unclear
- 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
Craft CMS, a content management system, is affected by a privilege escalation flaw that lets an attacker remotely, without logging in, reclaim a deactivated non-admin account through public registration and keep that account's direct permissions, which can lead to takeover of a privileged account. The bug is reachable only when email verification is disabled, which is a non-default setup, so it does not apply to every installation.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Craft CMS from 5.0.0 before 5.11.2 contains a privilege escalation vulnerability that allows unauthenticated public registrants to reclaim deactivated non-admin accounts while retaining their direct permissions. Attackers can register using a deactivated account, set a new password, and inherit permissions stored in userpermissions_users, enabling privileged account takeover when email verification is disabled.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- 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 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.11.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- craftcms cms
From 5.0.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-124429
Is CVE-2026-124429 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?
A deactivated non-admin account can be reclaimed through public registration, and the reclaimed account keeps its old direct permissions under a newly chosen password. That can lead to takeover of a privileged account.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124429?
cms: from 5.0.0 before 5.11.2.Source: cve.now feed data
Am I affected, and how do I check?
Craft CMS versions from 5.0.0 before 5.11.2 are affected. The bug needs email verification to be disabled and a deactivated non-admin account that still holds direct permissions; check your version in the Craft control panel or composer.lock, and check the email verification setting in your project config.Source: vulncheck.com, github.com
How do I fix CVE-2026-124429?
Upgrade Craft CMS to 5.11.2 or later, which contains the fix.Source: vulncheck.com, github.com