GHSA-3ggv-qwcp-j6xg is a medium-severity (CVSS 5.9) CWE-204 vulnerability in mautic/core. O3 Security confirms whether GHSA-3ggv-qwcp-j6xg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mautic Vulnerable to User Enumeration via Response Timing
Real-World Exposure
mautic/core🐘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
Impact
The attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.
Patches
This vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.
Technical Details
The vulnerability was caused by different response times when:
- A valid username was provided (password hashing occurred)
- An invalid username was provided (no password hashing occurred)
The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.
Workarounds
No workarounds are available. Users should upgrade to the patched version.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mautic/core | ≥ 4.4.0&&< 4.4.17 | 4.4.17 |
| 🐘Packagist | mautic/core | ≥ 5.0.0-alpha&&< 5.2.8 | 5.2.8 |
| 🐘Packagist | mautic/core | ≥ 6.0.0-alpha&&< 6.0.5 | 6.0.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core. 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 to 4.4.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3ggv-qwcp-j6xg 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-3ggv-qwcp-j6xg 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-3ggv-qwcp-j6xg. 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-3ggv-qwcp-j6xg in your dependencies?
O3 detects GHSA-3ggv-qwcp-j6xg across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.