Staging Environment: Content and features may be unstable or change without notice.

Advisory Weakness Curation

CVE-2022-21705

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-79jw-2f46-wv22

Authenticated remote code execution in October CMS ### 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)

gitlab/packagist/october/october/CVE-2022-21705

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') Octobercms is a self-hosted CMS platform based on the Laravel PHP Framework. In affected versions user input was not properly sanitized before rendering.

gitlab/packagist/october/system/CVE-2022-21705

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') Octobercms is a self-hosted CMS platform based on the Laravel PHP Framework. In affected versions user input was not properly sanitized before rendering. 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. The issue has been patched in Build 474 (v1.0.474) and v1.1.10.