GHSA-xpc5-rr39-v8v2
HIGHMautic has an XSS in contact tracking and page hits report
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
mautic/core-lib🐘mautic/core-lib🐘mautic/core🐘mautic/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Prior to this patch, a stored XSS vulnerability existed in the contact tracking and page hits report.
Patches
Please update to 4.4.13 or 5.1.1 or later.
Workarounds
None
References
https://owasp.org/www-project-top-ten/2017/A7_2017-Cross-Site_Scripting_(XSS) https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/07-Input_Validation_Testing/02-Testing_for_Stored_Cross_Site_Scripting
If you have any questions or comments about this advisory:
Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mautic/core-lib | ≥ 1.0.0-beta4&&< 4.4.13 | 4.4.13 |
| 🐘Packagist | mautic/core-lib | ≥ 5.0.0-alpha&&< 5.1.1 | 5.1.1 |
| 🐘Packagist | mautic/core | ≥ 1.0.0-beta4&&< 4.4.13 | 4.4.13 |
| 🐘Packagist | mautic/core | ≥ 5.0.0-alpha&&< 5.1.1 | 5.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mautic/core-lib to 4.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xpc5-rr39-v8v2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xpc5-rr39-v8v2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-xpc5-rr39-v8v2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xpc5-rr39-v8v2 in your dependencies?
O3 detects GHSA-xpc5-rr39-v8v2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.