Cross-Site Scripting (XSS) in october/backend (CVE-2020-5298)
Summary
Cross-site scripting in october/backend (CVE-2020-5298). Risk of unauthorized operations or information disclosure. Exploitable via ImportExportController. Mitigation: upgrade to 1.0.466 or later.
Original description
The description as published by the source.
In OctoberCMS (october/october composer package) versions from 1.0.319 and before 1.0.466, a user with the ability to use the import functionality of the ImportExportController behavior can be socially engineered by an attacker to upload a maliciously crafted CSV file which could result in a reflected XSS attack on the user in question Issue has been patched in Build 466 (v1.0.466).
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-2020-5298 has been found in october/backend.
Attackers can target a specific entry point like ImportExportController over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade october/backend to 1.0.466 or later.
If unsure, ask your IT team or search "october/backend CVE-2020-5298" on the vendor's site.
CVE-2020-5298 (october/backend) — CWE-79
Attack vector: remote (network-reachable)
Attack surface: ImportExportController
Patched: 1.0.466 — apply immediately
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.
Cross-site scripting (XSS) (CWE-79) exists in october/backend. Attackers reach the vulnerable code path via ImportExportController.
Check the vendor advisory for the affected versions of october/backend. Attack surface: ImportExportController.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.466.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'october/backend' . 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/backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
october/backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade october/backend to 1.0.466ステージング環境で 1.0.466 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- report packetstormsecurity.com
- report seclists.org