Read the docs
TI-2025-18503 Aliases CVE-2025-24786GHSA-9r4c-jwx3-3j76

Path traversal opening Sqlite3 database in WhoDB

Priority HIGH 82CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · 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. While the application only displays Sqlite3 databases present in the directory `/db`, there is no path traversal prevention in place. This allows an unauthenticated attacker to open any Sqlite3 database present on the host machine that the application is running on. Affected versions of WhoDB allow users to connect to Sqlite3 databases. By default, the databases must be present in `/db/` (or alternatively `./tmp/` if development mode is enabled). If no databases are present in the default directory, the UI indicates that the user is unable to open any databases. The database file is an user-controlled value. This value is used in `.Join()` with the default directory, in order to get the full path of the database file to open. No checks are performed whether the database file that is eventually opened actually resides in the default directory `/db`. This allows an attacker to use path traversal (`../../`) in order to open any Sqlite3 database present on the system. 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

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.02728 86th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed whodb (clidey): 0.45.0github.com/clidey/whodb/core (Go): 0.0.0-20250127172032-547336ac73c8

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
clideywhodbbefore 0.45.00.45.0Patch availableCNA
—github.com/clidey/whodb/core (Go)before 0.0.0-20250127172032-547336ac73c80.0.0-20250127172032-547336ac73c8Patch availableGHSA-9r4c-jwx3-3j76
  • 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-20250127172032-547336ac73c8 Fixed in 0.0.0-20250127172032-547336ac73c8 Patch available GHSA-9r4c-jwx3-3j76

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:clidey:whodb:*:*:*:*:*:*:*:*before 0.45.0Vulnerableclidey
  • cpe:2.3:a:clidey:whodb:*:*:*:*:*:*:*:* Versions before 0.45.0 Vulnerable ·clidey

Remediation

  • Fix · CNA whodb (clidey) Fixed in 0.45.0
  • Fix · GHSA-9r4c-jwx3-3j76 github.com/clidey/whodb/core (Go) Fixed in 0.0.0-20250127172032-547336ac73c8 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-24786
  2. 2026-10-03 Alias added: GHSA-9r4c-jwx3-3j76

References

  • TI-2025-18504 Parameter injection in DB connection URIs leading to local file inclusion in WhoDB CVSS 3.1HIGH 8.6

Sources