Cross-Site Scripting (XSS) in oro/platform (CVE-2021-41236)
Summary
Cross-site scripting in oro/platform (CVE-2021-41236). Confidential information can be exposed externally. Mitigation: upgrade to 4.2.8 or later.
Original description
The description as published by the source.
Summary
Email template preview is vulnerable to XSS payload added to email template content. The attacker should have permission to create or edit an email template. For successful payload, execution attacked user should preview a vulnerable email template.
Workarounds
There are no workarounds that address this vulnerability.
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-41236 has been found in oro/platform.
Confidential information can be exposed externally.
What to do: upgrade oro/platform to 4.2.8 or later.
If unsure, ask your IT team or search "oro/platform CVE-2021-41236" on the vendor's site.
CVE-2021-41236 (oro/platform) — CWE-79
Attack vector: remote (network-reachable)
Patched: 4.2.8 — apply immediately
Workaround: There are no workarounds that address this vulnerability.
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 oro/platform.
Check the vendor advisory for the affected versions of oro/platform.
Severity: ?. Confidential information can be exposed externally.
Update to 4.2.8.
Workaround: There are no workarounds that address this vulnerability.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'oro/platform' . 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 'oro/platform' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
oro/platformを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no workarounds that address this vulnerability.パッチが適用されるまでの応急処置として、There are no workarounds that address this vulnerability. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade oro/platform to 4.2.8ステージング環境で 4.2.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com