Parameter injection in DB connection URIs leading to local file inclusion in WhoDB
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| clidey | whodb | before 0.45.0 | 0.45.0 | Patch available | CNA |
| — | github.com/clidey/whodb/core (Go) | before 0.0.0-20250127202645-8d67b767e005 | 0.0.0-20250127202645-8d67b767e005 | Patch available | GHSA-c7w4-9wv8-7x7c |
- whodb Vendorclidey Affected before 0.45.0 Fixed in 0.45.0 Patch available CNA
- github.com/clidey/whodb/core (Go) Vendor— Affected before 0.0.0-20250127202645-8d67b767e005 Fixed in 0.0.0-20250127202645-8d67b767e005 Patch available GHSA-c7w4-9wv8-7x7c
Remediation
- Fix · CNA whodb (clidey) Fixed in 0.45.0
- Fix · GHSA-c7w4-9wv8-7x7c github.com/clidey/whodb/core (Go) Fixed in 0.0.0-20250127202645-8d67b767e005 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2025-24787
- 2026-10-03 Alias added: GHSA-c7w4-9wv8-7x7c
References
Advisory 2
More clidey Whodb vulnerabilities
- TI-2025-18503 Path traversal opening Sqlite3 database in WhoDB CVSS 3.1CRITICAL 10.0
Sources
- CVE-2025-24787 · CVE Program
- CVE-2025-24787 · NVD
- FIRST EPSS
- GHSA-c7w4-9wv8-7x7c · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences