S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Feb 3, 2026

CVE-2025-24786 Scanner

CVE-2025-24786 Scanner - Path Traversal vulnerability in WhoDB

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.8k
Times Used
continuous scan runs
5.5k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-24786
9.1
CVSScritical
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
whodbby clidey
< 0.45.0
Updated Aug 22, 2026View on NVD →
Detail

WhoDB is a lightweight database manager used primarily to manage Sqlite3 databases, often favored for its simplicity and ease of deployment. It is popular among developers and database administrators for local and small-scale applications, particularly where overhead from more extensive database systems would be unnecessary. Its open-source nature makes it a favorite for customization and adaptation to specific needs in a variety of environments. However, reliance on its default configurations without updates can extend vulnerabilities across its networks. It leverages Python scripts to interact with SQLite databases, which allows seamless integration into numerous software solutions used worldwide. Therefore, keeping the software version updated is crucial to mitigate potential security risks.

Path Traversal Vulnerability allows attackers to gain unauthorized access to filesystem structures by manipulating file paths. In the context of WhoDB, this vulnerability exists due to inadequate validation when opening database files. This oversight allows unauthenticated attackers to navigate through directories and potentially access sensitive database files. Such vulnerabilities may expose critical information contained within inadvertently accessed files, posing a risk to data confidentiality. It is categorized under high-severity due to the external access it provides to a fundamental component of the host system. Resolving this vulnerability is essential for maintaining secure and resilient database management environments.

The Path Traversal vulnerability in WhoDB is specifically triggered when an attacker exploits the application's database filename input. By inputting paths like "../etc/secret.db", attackers can traverse the server's directory structure to access Sqlite3 databases of their choosing. The vulnerable endpoint for this attack is the '/api/query' API, which the application exposes to interact with database files. Exploitation involves sending crafted POST requests to this API endpoint, which uses unspecified Hostname parameters to execute unauthorized file access requests. The vulnerability resides in the application's failure to restrict or sanitize user-provided file paths, resulting in potential illicit access to sensitive system data.

Exploitation of the Path Traversal vulnerability in WhoDB can lead to significant security breaches. If successful, attackers may extract confidential information housed within the database files, including sensitive user data, passwords, and other confidential records. Such unauthorized access not only contravenes privacy regulations but may also provide attackers with leverage to further infiltrate the network. This could lead to larger-scale attacks involving data exfiltration or corruption, potentially resulting in operational disruptions. The exploitation's impact is compounded by the possibility of additional vulnerabilities being accessed through compromised configurations, amplifying the need for immediate remediation.

REFERENCES

Solution Advice
  • Upgrade WhoDB to version 0.45.0 or later to mitigate the Path Traversal vulnerability.
  • Implement additional input validation to restrict file path manipulation from external sources.
  • Consider isolating sensitive database files to prevent unauthorized access through exposed paths.
  • Regularly review and update access controls and authentication mechanisms across the application.
  • Conduct routine audits to identify and rectify security weaknesses that could enable similar vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.