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

High 8.6 Published Updated

Attackers can inject parameters into database connection URIs to read local files on the host machine via unsafe string concatenation.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-24787?

CVE-2025-24787 is a high-severity path traversal vulnerability in clidey whodb, published on 6 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-943

Which versions are affected by CVE-2025-24787?

3 open source packages ship an affected version, including github.com/clidey/whodb/core. It affects 1 product.

PackageAffectedFixed in
github.com/clidey/whodb/core GoAll versions0.0.0-20250127202645-8d67b767e005
github.com/clidey/whodb/core GoAll versions0.0.0-20250127202645-8d67b767e005
github.com/clidey/whodb/core GoAll versions0.0.0-20250127202645-8d67b767e005

Products include Clidey Whodb.

How do I fix CVE-2025-24787?

Upgrade github.com/clidey/whodb/core to 0.0.0-20250127202645-8d67b767e005 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2025-24787 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24787 exists.

Sources

Also known as GHSA-c7w4-9wv8-7x7c, GO-2025-3457.

Is CVE-2025-24787 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free