Cross-Site Scripting (XSS) in mautic/core (CVE-2020-35124)
Summary
Cross-site scripting in mautic/core (CVE-2020-35124). Successful exploitation can lead to full system takeover. Exploitable via Referer header. Mitigation: upgrade to 2.16.5 or later.
Original description
The description as published by the source.
A cross-site scripting (XSS) vulnerability in the assets component of Mautic before 3.2.4 allows remote attackers to inject executable JavaScript through the Referer header of asset downloads.
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-35124 has been found in mautic/core.
Attackers can target a specific entry point like Referer header over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade mautic/core to 2.16.5 or later.
If unsure, ask your IT team or search "mautic/core CVE-2020-35124" on the vendor's site.
CVE-2020-35124 (mautic/core) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Referer header
Patched: 2.16.5 — 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 mautic/core. Attackers reach the vulnerable code path via Referer header without authentication.
Check the vendor advisory for the affected versions of mautic/core. Attack surface: Referer header.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.16.5.
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 'mautic/core' . 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 'mautic/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mautic/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mautic/core to 2.16.5ステージング環境で 2.16.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory forum.mautic.org
- advisory horizon3.ai
- advisory mautic.org
- web github.com
- web github.com
- web packagist.org