CVE-2026-29113: craftcms cms · Cross-Site Request Forgery (CSRF)
Affects craftcms cmsSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 5.9.7 or 4.17.3 when convenient.
Data as of 27 Oct 2026, 05:11 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.9.7, 4.17.3, 4.17.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade cms to 5.9.7 or 4.17.3; craftcms/cms to 5.9.7 or 4.17.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| craftcmscms | Affected
| Fixed in
|
| craftcmscms | Affected
| Fixed in
|
GitHubcraftcms/cmspkg:github/craftcms/cmsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade Craft CMS to versions 4.17.4 or 5.9.7 or later, where this vulnerability is patched. Until upgrades can be applied, administrators should consider restricting editor access to trusted users only and monitor for unusual preview token generation activity. Implementing web application firewall (WAF) rules to detect and block suspicious requests to the /actions/preview/create-token endpoint can reduce exploitation risk. Additionally, enforcing strict Content Security Policy (CSP) headers and SameSite cookie attributes can help mitigate CSRF attack vectors. Educating editors about the risks of clicking on untrusted links while logged in can reduce the likelihood of successful CSRF attacks. Regularly auditing CMS logs for anomalous preview token creation and access patterns is recommended. Finally, developers should review custom plugins or integrations that interact with preview tokens to ensure they do not introduce similar CSRF weaknesses.
Description
Craft is a content management system (CMS). Prior to 4.17.3 and 5.9.7, Craft CMS has a CSRF issue in the preview token endpoint at /actions/preview/create-token. The endpoint accepts an attacker-supplied previewToken. Because the action does not require POST and does not enforce a CSRF token, an attacker can force a logged-in victim editor to mint a preview token chosen by the attacker. That token can then be used by the attacker (without authentication) to access previewed/unpublished content tied to the victim’s authorized preview scope. This vulnerability is fixed in 4.17.3 and 5.9.7.