craftcms/cms
Affected
- introduced
5.0.0-RC1, fixed5.10.6(ecosystem)
Fixed versions
5.10.6
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-72779
Craft CMS: Arbitrary file read via SplFileObject in non-sandboxed template contexts
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
allowAdminChanges must be true (default in dev/staging, recommended false in production)Limitations
allowAdminChanges must be true: production best practices recommend false, which prevents entry type configuration changesallowAdminChanges=true are rated lowcreate() function is blocked by the Twig sandbox, so this cannot be exploited via system email templates or any other sandboxed contextImpact
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 CRAFT_SECURITY_KEY, 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.
Medium Basis: The source's own band: MODERATE
5.0.0-RC1, fixed 5.10.6 (ecosystem)5.10.6
The export has no generic command for this ecosystem.
4.0.0-RC1, fixed 4.18.2 (ecosystem)4.18.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0