GHSA-v5wf-jg37-r9m5
CRITICALSQLpage vulnerable to public exposure of database credentials
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
sqlpageReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
If
- you are using a SQLPage version older than v0.11.1
- your SQLPage instance is exposed publicly
- the database connection string is specified in the
sqlpage/sqlpage.jsonconfiguration file (not in an environment variable) - the web_root is the current working directory (the default)
- your database is exposed publicly
then an attacker could retrieve the database connection information from SQLPage and use it to connect to your database directly.
Patches
Upgrade to v0.11.1 as soon as possible.
Workarounds
If you cannot upgrade immediately:
- Using an environment variable instead of the configuration file to specify the database connection string prevents exposing it on vulnerable versions.
- Using a different web root (that is not a parent of the SQLPage configuration directory) fixes the issue.
- And in any case, you should generally avoid exposing your database publicly
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | sqlpage | all versions | 0.11.1 |
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 sqlpage. 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 sqlpage to 0.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v5wf-jg37-r9m5 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-v5wf-jg37-r9m5 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-v5wf-jg37-r9m5. 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-v5wf-jg37-r9m5 in your dependencies?
O3 detects GHSA-v5wf-jg37-r9m5 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.