Summary
A low-privilege user (or an unauthenticated user who has been sent a shared URL) can escalate their privileges to admin by abusing UsersController->actionImpersonateWithToken.
Affected users should update to Craft 4.17.6 and 5.9.12 to mitigate the issue.
Details
I am a security researcher at Anthropic. I am using LLMs to identify vulnerabilities in open-source software and have spent some time looking at Craft CMS.
I believe I have found a fairly serious bug. While an LLM initially found this bug, I manually validated it and wrote this email myself.
This vulnerability allows any low-privilege user to escalate their privileges and become an admin, or, in extreme circumstances, unprivileged users to do the same.
Therefore, this vulnerability affects Craft Pro and Team more than Craft Solo.
Specifically, an attacker who possesses a valid “preview token” can then append &action=users/impersonate-with-token&userId=1&prevUserId=1 to the preview URL to hijack the request into the impersonation endpoint, logging in as any user (including admin) without authentication. Getting the preview token is easy, and all an editor would have to do is create a single article, click “Preview”, and then recover this token.
From the best of my understanding of the code, here’s what happens:
- The action re-dispatch in
actionPreview() passes $skipSpecialHandling=true to handleRequest(), bypassing all security guards, and passes $checkToken=false to checkIfActionRequest(), which allows an attacker-controlled action query parameter to override the dispatch target.
- The
requireToken() guard on actionImpersonateWithToken() only checks a boolean (_hadToken) that was set when the preview token was initially resolved. It does not verify that the token was intended for the impersonation action, and so any valid token from any route satisfies the check.
actionImpersonateWithToken is listed in $allowAnonymous and performs no authorization beyond requireToken(), so no prior authentication is required.
PoC
I have a working PoC that achieves full admin takeover on the latest Craft CMS 5.9.10. Spawn a local version of Craft. Then, you’ll want to log in and create a valid setup:
- Log in at http://host:18895/admin
- Go to Settings, Sections, New Section (name: "Blog", type: "Channel")
- Under Site Settings, set URI Format to blog/{slug}
- Then go to Entries, New Entry, Blog, and give it any title
Next, obtain a preview token
- Open the saved entry in the editor
- Click the Preview button
- A preview pane opens with the entry rendered in an iframe
- Right-click inside the preview pane and Inspect Element
- Find the <iframe> element; its src contains the tokenized URL:
http://host:18895/blog/title?x-craft-live-preview=...&token=XXXXXXXX
- Copy the
token= value
Finally, execute the exploit:
1. Open a new incognito/private browser window
2. Navigate to: http://host:18895/?token=XXXXXXXX&action=users/impersonate-with-token&userId=1&prevUserId=1
3. You may see a 404. This is expected.
To verify the exploit, in the same incognito tab, navigate to http://host:18895/admin. You should land on the admin dashboard, logged in as admin, without ever entering credentials.
Impact
Privilege escalation; everyone is impacted.
References
6301e21
Summary
A low-privilege user (or an unauthenticated user who has been sent a shared URL) can escalate their privileges to admin by abusing
UsersController->actionImpersonateWithToken.Affected users should update to Craft 4.17.6 and 5.9.12 to mitigate the issue.
Details
I am a security researcher at Anthropic. I am using LLMs to identify vulnerabilities in open-source software and have spent some time looking at Craft CMS.
I believe I have found a fairly serious bug. While an LLM initially found this bug, I manually validated it and wrote this email myself.
This vulnerability allows any low-privilege user to escalate their privileges and become an admin, or, in extreme circumstances, unprivileged users to do the same.
Therefore, this vulnerability affects Craft Pro and Team more than Craft Solo.
Specifically, an attacker who possesses a valid “preview token” can then append
&action=users/impersonate-with-token&userId=1&prevUserId=1to the preview URL to hijack the request into the impersonation endpoint, logging in as any user (including admin) without authentication. Getting the preview token is easy, and all an editor would have to do is create a single article, click “Preview”, and then recover this token.From the best of my understanding of the code, here’s what happens:
actionPreview()passes$skipSpecialHandling=truetohandleRequest(), bypassing all security guards, and passes$checkToken=falsetocheckIfActionRequest(), which allows an attacker-controlled action query parameter to override the dispatch target.requireToken()guard onactionImpersonateWithToken()only checks a boolean (_hadToken) that was set when the preview token was initially resolved. It does not verify that the token was intended for the impersonation action, and so any valid token from any route satisfies the check.actionImpersonateWithTokenis listed in$allowAnonymousand performs no authorization beyondrequireToken(), so no prior authentication is required.PoC
I have a working PoC that achieves full admin takeover on the latest Craft CMS 5.9.10. Spawn a local version of Craft. Then, you’ll want to log in and create a valid setup:
Next, obtain a preview token
http://host:18895/blog/title?x-craft-live-preview=...&token=XXXXXXXXtoken=valueFinally, execute the exploit:
1. Open a new incognito/private browser window
2. Navigate to:
http://host:18895/?token=XXXXXXXX&action=users/impersonate-with-token&userId=1&prevUserId=13. You may see a 404. This is expected.
To verify the exploit, in the same incognito tab, navigate to
http://host:18895/admin. You should land on the admin dashboard, logged in as admin, without ever entering credentials.Impact
Privilege escalation; everyone is impacted.
References
6301e21