GHSA-m2hh-2m46-x6j5 is a medium-severity (CVSS 6.5) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.
silverstripe/framework may disclose database credentials during connection failure
Real-World Exposure
silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/frameworkReal-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
When running SilverStripe 3.7 or 4.x in dev mode with the mysqli database driver, there is a potential to disclose the connection details.
We have blacklisted the sensitive parts of the connection information from being included in dev mode stack traces when database errors occur.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/framework | ≥ 3.7.0-rc1&&< 3.7.1 | 3.7.1composer require silverstripe/framework:^3.7.1 |
| 🐘Packagist | silverstripe/framework | ≥ 4.0.0-rc1&&< 4.0.5 | 4.0.5composer require silverstripe/framework:^4.0.5 |
| 🐘Packagist | silverstripe/framework | ≥ 4.1.0-rc1&&< 4.1.3 | 4.1.3composer require silverstripe/framework:^4.1.3 |
| 🐘Packagist | silverstripe/framework | ≥ 4.2.0-rc1&&< 4.2.2 | 4.2.2composer require silverstripe/framework:^4.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/framework to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2hh-2m46-x6j5 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m2hh-2m46-x6j5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-m2hh-2m46-x6j5. 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-m2hh-2m46-x6j5 in your dependencies?
O3 Security finds GHSA-m2hh-2m46-x6j5 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.