CVE-2026-46696: October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls
A vulnerability was identified in the Twig sandbox security policy that allowed a chained bypass when cms.safemode is enabled. The Laravel session store was exposed to Twig with unrestricted method access, and raw SQL methods reachable through Eloquent's call forwarding were not blocked across the full builder chain.
Published Sep 14, 2026
Affected packages
october/system
- Ecosystem
- Composer (PHP)
- Affected
- < 3.7.17
- Fixed in
- 3.7.17
- Check
composer show october/system
october/system
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.0.0, < 4.2.23
- Fixed in
- 4.2.23
- Check
composer show october/system
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A vulnerability was identified in the Twig sandbox security policy that allowed a chained bypass when cms.safe_mode is enabled. The Laravel session store was exposed to Twig with unrestricted method access, and raw SQL methods reachable through Eloquent's __call forwarding were not blocked across the full builder chain. When combined, a backend user with CMS markup editing access could read arbitrary database values via raw SQL expressions and write to the backend authentication session key, forging a backend session as another existing user.
Scope of impact is narrow. Safe Mode is a niche feature, primarily used for demo installations and multi-tenant or shared-editor scenarios where untrusted users are deliberately granted access to the CMS markup editor. Standard production deployments do not enable Safe Mode, because under normal October CMS guidance backend access - including markup editing - is restricted to trusted administrators, and direct PHP injection through markup is already possible without Safe Mode in that configuration.
This issue only affects sites that meet all of the following conditions:
cms.safe_modeis enabled (a deliberate opt-in for demos or untrusted-editor scenarios)- The site has at least one backend user with CMS markup editing access who is not intended to be trusted as a full administrator
- The site has at least one existing superuser account whose session the lower-privileged user can impersonate
Impact
- Arbitrary read access to database tables, including superuser persistence codes from
backend_users, via raw SQL expressions reachable throughEloquent\Model,Eloquent\Builder, or any allowlisted class that__call-forwards to a query builder - Forgery of a backend authentication session by writing to the
admin_authsession key from a Twig template, allowing a markup editor to impersonate an existing superuser - Requires authenticated backend access with CMS markup editing permission AND
cms.safe_modeenabled - Not exploitable when Safe Mode is disabled (direct PHP injection through markup is already possible in that configuration, so Safe Mode is the boundary this issue affects)
Patches
The vulnerability has been patched in v3.7.17 and v4.2.21. The Laravel session store is now wrapped in a proxy that exposes only an explicit subset of read/write methods and rejects writes to reserved session key prefixes (admin_auth, october_auth, login_*, _token, and other framework internals). Raw SQL and subquery methods (selectRaw, whereRaw, orderByRaw, joinSub, and related) are now blocked on Query\Builder, Eloquent\Builder, and Eloquent\Model so the blocklist is consistent across the __call forwarding chain. All sites that enable cms.safe_mode are encouraged to upgrade to the latest patched version.
Workarounds
If upgrading immediately is not possible:
- Restrict CMS markup editing access to fully trusted administrators only - the standard October CMS recommendation for any deployment
- Note that disabling
cms.safe_modeis not a workaround; Safe Mode is the boundary this issue affects, and disabling it removes the only sandbox between markup editors and the server
References
- Reported by r00tn0b0dy
Credited to r00tn0b0dy.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-49400
October CMS: PHP Object Injection via Backend Widget Session Storage
low3.3Sep 14, 2026CVE-2026-26067
October CMS has Safe Mode Bypass via CSS Preprocessor Compilers
medium4.9Apr 21, 2026CVE-2026-27937
October CMS: Reflected XSS via DataTable Form Widget
low3.1No fixApr 21, 2026CVE-2026-29179
October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations
low3.3Apr 21, 2026CVE-2026-24906
October CMS has Stored XSS in Backend Editor Markup Classes
medium5.4Apr 14, 2026CVE-2026-24907
October CMS has Stored XSS in Event Log Mail Preview
medium5.4Apr 14, 2026
