Vulnerability in october/system (CVE-2021-32649)
Summary
Vulnerability in october/system (CVE-2021-32649). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.473 or later.
Original description
The description as published by the source.
October CMS is a self-hosted content management system (CMS) platform based on the Laravel PHP Framework. Prior to versions 1.0.473 and 1.1.6, an attacker with "create, modify and delete website pages" privileges in the backend is able to execute PHP code by running specially crafted Twig code in the template markup. The issue has been patched in Build 473 (v1.0.473) and v1.1.6. Those unable to upgrade may apply the patch to their installation manually as a workaround.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32649 has been found in october/system.
Successful exploitation can lead to full system takeover.
What to do: upgrade october/system to 1.0.473 or later.
If unsure, ask your IT team or search "october/system CVE-2021-32649" on the vendor's site.
CVE-2021-32649 (october/system) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.0.473 — apply immediately
Workaround: Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in october/system.
Check the vendor advisory for the affected versions of october/system.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.0.473.
Workaround: Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'october/system' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'october/system' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
october/systemを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade.パッチが適用されるまでの応急処置として、Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade october/system to 1.0.473ステージング環境で 1.0.473 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com