Authenticated remote code execution in October CMS
Published 23 Feb 2022 · Updated 19 Feb 2024
Affected packages
- Affected
- <1.0.474
- Fixed in
- 1.0.474
composer require october/system:^1.0.474- Affected
- >=1.1.0 <1.1.10
- Fixed in
- 1.1.10
composer require october/system:^1.1.10- Affected
- >=2.0.0 <2.1.27
- Fixed in
- 2.1.27
composer require october/system:^2.1.27Details
Impact
An authenticated user with the permissions to create, modify and delete website pages can exploit this vulnerability to bypass cms.safe_mode / cms.enableSafeMode in order to execute arbitrary code.
- This issue only affects admin panels that rely on safe mode and restricted permissions.
- To exploit this vulnerability, an attacker must first have access to the backend area.
Patches
The issue has been patched in Build 474 (v1.0.474) and v1.1.10.
Workarounds
Apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe to your installation manually if unable to upgrade to Build 474 or v1.1.10.
References
Credits to:
- David Miller
For more information
If you have any questions or comments about this advisory:
- Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
Is GHSA-79jw-2f46-wv22 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.