Cross-Site Scripting (XSS) in mautic/core (CVE-2022-25772)
Summary
Cross-site scripting in mautic/core (CVE-2022-25772). Confidential information can be exposed externally. Mitigation: upgrade to 4.3.0 or later.
Original description
The description as published by the source.
Impact
Mautic allows you to track open rates by using tracking pixels.
The tracking information is stored together with extra metadata of the tracking request.
The output isn't sufficiently filtered when showing the metadata of the tracking information, which may lead to a vulnerable situation.
Patches
Please upgrade to 4.3.0
Workarounds
None.
References
- Internally tracked under MST-38
For more information
If you have any questions or comments about this advisory:
- Email us at security@mautic.org
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-2022-25772 has been found in mautic/core.
Confidential information can be exposed externally.
What to do: upgrade mautic/core to 4.3.0 or later.
If unsure, ask your IT team or search "mautic/core CVE-2022-25772" on the vendor's site.
CVE-2022-25772 (mautic/core) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Patched: 4.3.0 — 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.
Check the vendor advisory for the affected versions of mautic/core.
Severity: ?. Confidential information can be exposed externally.
Update to 4.3.0.
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 4.3.0ステージング環境で 4.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web intel.com