CVE-2025-24786

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 51.8%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
10.0
EG Score
10.0(medium)
EPSS
83.8%
KEV
Not listed

Published

February 6, 2025

Last Modified

December 31, 2025

Advisory Details (3)

Auto-updated Jul 18, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Path traversal opening Sqlite3 database · Advisory · clidey/whodb · GitHub

https://github.com/clidey/whodb/security/advisories/GHSA-9r4c-jwx3-3j76
generic

whodb/core/src/plugins/sqlite3/db.go at ba6eb81d0ca40baead74bca58b2567166999d6a6 · clidey/whodb · GitHub

https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L26
generic

whodb/core/src/plugins/sqlite3/db.go at ba6eb81d0ca40baead74bca58b2567166999d6a6 · clidey/whodb · GitHub

https://github.com/clidey/whodb/blob/ba6eb81d0ca40baead74bca58b2567166999d6a6/core/src/plugins/sqlite3/db.go#L14-L20

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/clidey/whodb/core—0.0.0-20250127172032-547336ac73c8—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-19 14:30 UTCEPSS rescore
  2. 2026-07-19 14:30 UTCEPSS rescore
  3. 2026-07-19 02:28 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-18 10:03 UTCEPSS rescore
  6. 2026-07-16 17:02 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 01:59 UTCEPSS rescore
  10. 2026-07-13 22:29 UTCEPSS rescore
  11. 2026-07-13 22:29 UTCEPSS rescore
  12. 2026-07-13 06:12 UTCEPSS rescore
  13. 2026-07-13 06:12 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 08:26 UTCEPSS rescore
  18. 2026-07-09 19:09 UTCEPSS rescore
  19. 2026-07-08 15:14 UTCEPSS rescore
  20. 2026-07-07 13:45 UTCEPSS rescore
  21. 2026-07-07 11:51 UTCOSV refresh
  22. 2026-07-06 16:26 UTCEPSS rescore
  23. 2026-07-06 02:22 UTCEPSS rescore
  24. 2026-07-06 02:22 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 52 more
  1. 2026-07-04 06:30 UTCEPSS rescore
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-06-30 23:21 UTCEPSS rescore
  4. 2026-06-30 23:21 UTCEPSS rescore
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 04:55 UTCEPSS rescore
  7. 2026-06-28 04:55 UTCEPSS rescore
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 14:04 UTCEPSS rescore
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-23 21:32 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-18 22:43 UTCOSV refresh
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-17 17:52 UTCEPSS rescore
  28. 2026-06-16 17:52 UTCEPSS rescore
  29. 2026-06-16 17:52 UTCEPSS rescore
  30. 2026-06-15 17:48 UTCEPSS rescore
  31. 2026-06-14 23:17 UTCEPSS rescore
  32. 2026-06-12 23:11 UTCEPSS rescore
  33. 2026-06-11 13:59 UTCEPSS rescore
  34. 2026-06-10 22:18 UTCEPSS rescore
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-08 14:16 UTCEPSS rescore
  37. 2026-06-08 14:16 UTCEPSS rescore
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-06 13:47 UTCEPSS rescore
  40. 2026-06-05 22:46 UTCEPSS rescore
  41. 2026-06-05 22:46 UTCEPSS rescore
  42. 2026-06-05 06:10 UTCEPSS rescore
  43. 2026-06-05 06:10 UTCEPSS rescore
  44. 2026-06-04 13:11 UTCEPSS rescore
  45. 2026-06-04 13:11 UTCEPSS rescore
  46. 2026-06-02 20:12 UTCEPSS rescore
  47. 2026-06-02 20:12 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-30 12:09 UTCEG score recompute
  51. 2026-05-30 10:05 UTCOSV refresh
  52. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2025/CVE-2025-24786.yaml
    First seen Jan 1, 2025

    WhoDB < 0.45.0 - Path Traversal

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-24786?
CVE-2025-24786 is a critical vulnerability published on February 6, 2025. 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…
When was CVE-2025-24786 disclosed?
CVE-2025-24786 was first published in the National Vulnerability Database on February 6, 2025, with the most recent update on December 31, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24786 actively exploited?
CVE-2025-24786 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-24786?
CVE-2025-24786 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2025-24786?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24786, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-24786

Explore →

Is Your Infrastructure Affected by CVE-2025-24786?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs