GHSA-4hjq-422q-4vpx
MEDIUMGHSA-4hjq-422q-4vpx is a medium-severity (CVSS 5.8) Information Exposure vulnerability in mautic/core. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-4hjq-422q-4vpx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mautic vulnerable to secret data exfiltration via symfony parameters
Real-World Exposure
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
Symfony parameters (which is what Mautic transforms configuration parameters into) can be used within other Symfony parameters by design. However, this also means that an admin who is normally not privy to certain parameters, such as database credentials, could expose them by leveraging any of the free text fields in Mautic’s configuration that are used in publicly facing parts of the application.
For example,
- Go to Configuration page -> Landing Page Settings -> Analytics script and enter this: <
script> console.log("db password is: %mautic.db_password%"); </script> - Visit any landing page and open the JS dev console. You will see the following message with real instance db password:
db password is: <real password>
Risk rating: ModerateCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:L
Patches
Upgrade to 3.3.2
Workarounds
No
References
No
For more information
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 | all versions | 3.3.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
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 3.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4hjq-422q-4vpx 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-4hjq-422q-4vpx 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-4hjq-422q-4vpx. 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-4hjq-422q-4vpx in your dependencies?
O3 detects GHSA-4hjq-422q-4vpx across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.