October CMS has Safe Mode Bypass via CSS Preprocessor Compilers
Published 21 Apr 2026 · Updated 5 May 2026
Affected packages
- Affected
- <3.7.14
- Fixed in
- 3.7.14
composer require october/system:^3.7.14- Affected
- >=4.0.0 <4.1.10
- Fixed in
- 4.1.10
composer require october/system:^4.1.10Details
A server-side information disclosure vulnerability was identified in the handling of CSS preprocessor files. Backend users with Editor permissions could craft .less, .sass, or .scss files that leverage the compiler's import functionality to read arbitrary files from the server. This worked even with cms.safe_mode enabled.
Impact
- Potential exposure of sensitive server-side files
- Requires authenticated backend access with Editor permissions
- Only relevant when
cms.safe_modeis enabled (otherwise direct PHP injection is already possible)
Patches
The vulnerability has been patched in v3.7.14 and v4.1.10. When cms.safe_mode is enabled, .less, .sass, and .scss files can no longer be created, uploaded, or edited across the CMS editor, media manager, and file upload interfaces. All users are encouraged to upgrade to the latest patched version.
Workarounds
If upgrading immediately is not possible:
- Set
cms.editable_asset_typesconfig to['css', 'js']to remove preprocessor file types from the editor - Restrict Editor tool access to fully trusted administrators only
- Reported by Chris Alupului
Is GHSA-3888-q23f-x7qh in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected october/system, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.