Skip to main content
Public proof of conceptFix available

CVE-2025-24786

A public proof of concept exists; no exploitation attested.

  • Published2025-02-06
  • Fixed in0.45.0
  • WeaknessCWE-22 · CWE-35

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-02-0619:15CVE publishedNVD

Versions per branch

NVD · OSV
Clidey whodb
BranchAffectedFixed in
0.45< 0.45.00.45.0
clidey/whodb/core
BranchAffectedFixed in
0.0< 0.0.0-20250127172032-547336ac73c80.0.0-20250127172032-547336ac73c8

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • clidey whodb
    Affected
    • = < 0.45.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-02-06

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • govulncheck-vulndbSUSE:Linux Enterprise Module for Package Hub 15 SP6all versions · fixed in 0.0.20250207T224745-150000.1.32.1
  • govulncheck-vulndbopenSUSE:Tumbleweedall versions · fixed in 0.0.20250207T224745-1.1
  • govulncheck-vulndbopenSUSE:Leap 15.6all versions · fixed in 0.0.20250207T224745-150000.1.32.1

Full record on NVD

Fix

  1. Update Clidey whodb to 0.45.0

Advisories and patches

Detection

read 2026-11-20 11:10 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2025-02-06
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-9r4c-jwx3-3j76

Frequently asked questions

What is CVE-2025-24786?

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.

Is CVE-2025-24786 actively exploited?

A proof-of-concept exploit exists for CVE-2025-24786, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2025-24786?

CVE-2025-24786 has a CVSS v3 base score of 9.1 (Critical severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running govulncheck-vulndb? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record