How severe is GHSA-m2hh-2m46-x6j5?

GHSA-m2hh-2m46-x6j5 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m2hh-2m46-x6j5?

GHSA-m2hh-2m46-x6j5 affects the following packages: silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-m2hh-2m46-x6j5?

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.

How do I detect GHSA-m2hh-2m46-x6j5 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework. 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.

How do I mitigate GHSA-m2hh-2m46-x6j5 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-m2hh-2m46-x6j5?

O3 pinpoints whether GHSA-m2hh-2m46-x6j5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m2hh-2m46-x6j5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m2hh-2m46-x6j5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-m2hh-2m46-x6j5 published, and has it been updated?

GHSA-m2hh-2m46-x6j5 was published on May 28, 2024 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-m2hh-2m46-x6j5

MEDIUM

silverstripe/framework may disclose database credentials during connection failure

Published

May 28, 2024

Updated

Dec 3, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/framework`	≥ 3.7.0-rc1&&< 3.7.1	3.7.1
🐘Packagist	`silverstripe/framework`	≥ 4.0.0-rc1&&< 4.0.5	4.0.5
🐘Packagist	`silverstripe/framework`	≥ 4.1.0-rc1&&< 4.1.3	4.1.3
🐘Packagist	`silverstripe/framework`	≥ 4.2.0-rc1&&< 4.2.2	4.2.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework. 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 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 pinpoints whether GHSA-m2hh-2m46-x6j5 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-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

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.

O3 Security · Impact-Aware SCA

Is GHSA-m2hh-2m46-x6j5 in your dependencies?

O3 detects GHSA-m2hh-2m46-x6j5 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works