craftcms/cms security advisory

CVE-2026-29113: Craft CMS has a potential information disclosure vulnerability in preview tokens

CVE-2026-29113 is a low-severity information disclosure vulnerability in the PHP package craftcms/cms (CVSS 4.3), published 10 March 2026. It is fixed in 4.17.3 and 5.9.7, one per release line; earlier versions on each line are affected. It can be exploited without an account.

low 4.3 published 2026-03-10 · updated 2026-09-02

Affected versions: >= 4.0.0-RC1, < 4.17.3
>= 5.0.0-RC1, < 5.9.7
Fixed in: 4.17.3, 5.9.7
Newest release: 5.12.0
Severity: Low · CVSS 4.3
Type: Information disclosure
CWE-352
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your craftcms/cms version affected?

Run composer show craftcms/cms in your project, then enter the version. We check it against this and every other known craftcms/cms advisory.

Who can exploit CVE-2026-29113

Access: No account. Anyone who can send a request to an app that uses the affected code.
Interaction: A user also has to do something, such as open a link or a page the attacker prepared.

CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Your app is only exposed if it uses the affected part of craftcms/cms. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-29113 in craftcms/cms

Find the installed version: composer show craftcms/cms. If you never required it yourself, composer why craftcms/cms shows which package pulls it in.
Update it: composer update craftcms/cms --with-all-dependencies. You need the fixed version for your release line (4.17.3 and 5.9.7).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "craftcms/cms": "^5.9.7" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-29113.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for information disclosure issues while the upgrade waits. None of it replaces the fix.

Make sure APP_DEBUG (or your framework's debug mode) is off in production and error pages show no stack traces.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-29113 advisory

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.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-29113. Advisory title: “Craft CMS has a potential information disclosure vulnerability in preview tokens”.

References

GitHub advisory GHSA-vg3j-hpm9-8v5v github.com
Fix commit 6a88468 github.com

Other craftcms/cms advisories

critical Craft CMS: Passkey login accepts replayed WebAuthn assertions 2026-08-07
medium CVE-2026-72779: Craft CMS: Arbitrary file read via SplFileObject in non-sandboxed template contexts 2026-08-06
medium CVE-2026-72782: Craft CMS: Authenticated leak of secret environment variables 2026-08-06
medium CVE-2026-72785: Craft CMS: Authorization bypass: view-only Categories user can modify category structure via structures/move-element 2026-08-06
medium CVE-2026-14794: Craft CMS: Missing authorization check allows non-admin control panel users access to user registration metrics 2026-08-06
low CVE-2026-72783: Craft CMS: Incorrect path validation could potentially lead to path traversal 2026-08-06

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.