CVE-2026-46696
Received Received - Intake

Session Forgery in October CMS via Twig Sandbox Bypass

Vulnerability report for CVE-2026-46696, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: GitHub, Inc.

Description

October System provides the system module for October Content Management System. Versions prior to 3.7.17 and 4.2.21 have a vulnerability 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. The 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_mode` is 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; and the site has at least one existing superuser account whose session the lower-privileged user can impersonate. 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. A workaround is available. Restrict CMS markup editing access to fully trusted administrators only - the standard October CMS recommendation for any deployment. Note that disabling `cms.safe_mode` is not a workaround; Safe Mode is the boundary this issue affects, and disabling it removes the only sandbox between markup editors and the server.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-14
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
october october_cms to 4.2.21 (exc)
october october_cms 3.7.17
october october_cms 4.2.21

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-269 The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects October CMS versions before 3.7.17 and 4.2.21. It involves a sandbox bypass in the Twig security policy when Safe Mode is enabled. A backend user with CMS markup editing access could exploit unrestricted Laravel session store access in Twig and unblocked raw SQL methods through Eloquent to read database values and forge backend sessions as another user.

Detection Guidance

Check if your October CMS version is below 3.7.17 or 4.2.21 by running: composer show october/october. If Safe Mode is enabled, verify if any backend user has CMS markup editing access. Inspect session storage for unauthorized writes to keys like admin_auth or october_auth.

Impact Analysis

The impact is limited to sites with specific conditions: Safe Mode enabled, untrusted markup editors, and existing superuser accounts. An attacker could impersonate a superuser by forging a backend session, potentially gaining elevated privileges. Standard production sites without Safe Mode are unaffected.

Compliance Impact

This vulnerability has a narrow scope and primarily affects October CMS installations with Safe Mode enabled, untrusted markup editors, and existing superuser accounts. It does not directly violate GDPR or HIPAA but could indirectly impact compliance if exploited to access or modify sensitive data. The risk is limited to specific configurations where untrusted users have markup editing access.

Mitigation Strategies

Upgrade October CMS to version 3.7.17 or 4.2.21 or later. Restrict CMS markup editing access to fully trusted administrators only. Do not rely on disabling Safe Mode as a workaround.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46696. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart