CVE-2026-29113: Craft has a potential information disclosure vulnerability in preview tokens
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.
Security readout for executives and security teams
Plain-English summary
A remote attacker could trick a logged-in Craft CMS editor into creating an attacker-chosen preview token. The attacker could then use that token without authentication to view unpublished content within the editor’s authorized preview scope. The issue does not affect integrity or availability, and exploitation requires victim interaction.
Executive priority
Schedule prompt remediation through the normal patch cycle. Escalate timing for public-facing CMS deployments holding sensitive unpublished material. The low severity reflects limited confidentiality impact, required user interaction, and no indicated integrity or availability impact.
Technical view
CVE-2026-29113 is a CWE-352 CSRF flaw in /actions/preview/create-token. Affected versions accept a supplied previewToken without requiring POST or enforcing CSRF validation. Successful abuse exposes previewed or unpublished content authorized for the victim. Craft CMS 4.17.3 and 5.9.7 contain the fix.
Likely exposure
Exposure exists on Craft CMS versions 4.0.0-RC1 through 4.17.2 and 5.0.0-RC1 through 5.9.6. Practical risk is greatest where editors are logged in and unpublished content is sensitive. The attacker needs network access to the application and victim interaction.
Exploitation context
The CVSS 4.0 score is 2.3. Exploitation requires a logged-in authorized editor to interact with attacker-controlled content. The resulting token only reaches content within that editor’s preview scope. The supplied sources do not report active exploitation, and this CVE is not identified as KEV.
Researcher notes
Affected ranges begin with 4.0.0-RC1 and 5.0.0-RC1. The weakness is CWE-352 with CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Evidence supports scoped confidentiality loss only; no active exploitation evidence appears in the bundle.
Mitigation direction
Upgrade Craft CMS 4.x installations to version 4.17.3 or later.
Upgrade Craft CMS 5.x installations to version 5.9.7 or later.
Consult the Craft security advisory for vendor guidance and deployment considerations.
Prioritize systems containing confidential drafts or unpublished business information.
Validation and detection
Inventory Craft CMS versions across production, staging, preview, and editorial environments.
Confirm every 4.x instance runs 4.17.3 or later.
Confirm every 5.x instance runs 5.9.7 or later.
Verify the preview token endpoint enforces the corrected request and CSRF controls.
Review available access records for unexpected use of preview tokens.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.