CVE-2026-72779: Craft CMS: Arbitrary file read via SplFileObject in non-sandboxed template contexts
Craft CMS 5.0.0-RC1 before 5.10.6 and 4.0.0-RC1 before 4.18.2 contain an arbitrary file read vulnerability. The create() Twig function restricts class instantiation using a 5-entry blocklist that does not include SplFileObject, allowing an authenticated administrator (with allowAdminChanges=true) to configure a malicious entry type title or URI format that instantiates SplFileObject in a non-sandboxed template context. When a user subsequently creates an entry in the affected section, arbitrary files on the server (such as .env containing the security key and database credentials) are read and rendered as entry titles.
Other sources
Craft CMS: Arbitrary file read via SplFileObject in non-sandboxed template contexts
— Packagist
The create() Twig function (introduced in 5.9.0) allows instantiation of arbitrary PHP classes from template code, restricted only by a 5-entry blocklist. SplFileObject is not in the blocklist, enabling arbitrary file read, including .env (security key, DB credentials) and the passwd file from non-sandboxed Twig template contexts, such as entry type title formats and URI formats.
The sandbox correctly blocks create() in system email templates, so this finding applies only to admin-configured, non-sandboxed contexts that require allowAdminChanges=true.
Prerequisites
- Admin access to the Craft control panel - allowAdminChanges must be true (default in dev/staging, recommended false in production) - Admin must be able to edit entry type settings (title format, URI format) - Any user who subsequently creates an entry in the affected section triggers the file read
Limitations
- Requires admin-level access: not exploitable by low-privilege users - allowAdminChanges must be true: production best practices recommend false, which prevents entry type configuration changes - Per Craft’s own severity guidelines, findings requiring allowAdminChanges=true are rated low - The create() function is blocked by the Twig sandbox, so this cannot be exploited via system email templates or any other sandboxed context
Impact
An admin user (or an attacker who has compromised an admin account) can read arbitrary files from the server filesystem by setting a malicious entry type title format using create('SplFileObject', ['/path/to/file']). In production environments, this exposes .env files containing the CRAFTSECURITYKEY, database credentials, API keys, and other secrets. The file contents are rendered as entry titles visible to any user with permission to view entries in the affected section.
The impact is limited by the requirement for admin access and allowAdminChanges=true.
— GitHub
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/craftcms/cmsto a version that resolves this vulnerability.Fixed in 4.18.2 - Upgrade
Upgrade
composer/craftcms/cmsto a version that resolves this vulnerability.Fixed in 5.10.6 - Upgrade
Upgrade
Craft CMSto a version that resolves this vulnerability.Fixed in 5.10.6 - Upgrade
Upgrade
Craft CMSto a version that resolves this vulnerability.Fixed in 4.18.2 - Configuration
Set allowAdminChanges to false, especially in production, to prevent entry type configuration changes.
Craft CMS allowAdminChanges = false
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72779?
CVE-2026-72779 has a severity rating of medium, with a score of 4.5.
How do I fix CVE-2026-72779?
To fix CVE-2026-72779, upgrade Craft CMS to version 5.10.6 or 4.18.2 or later.
What systems are affected by CVE-2026-72779?
CVE-2026-72779 affects Craft CMS versions 5.0.0-RC1 before 5.10.6 and 4.0.0-RC1 before 4.18.2.
What type of vulnerability is CVE-2026-72779?
CVE-2026-72779 is classified as an arbitrary file read vulnerability.
Who can exploit CVE-2026-72779?
An authenticated administrator with the allowAdminChanges=true setting can exploit CVE-2026-72779.