CVE-2025-10118
BaseFortify
Publication date: 2025-09-09
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| emiloi | e-logbook_with_health_monitoring_system_for_covid-19 | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10118 is a critical SQL injection vulnerability in the itsourcecode E-Logbook with Health Monitoring System for COVID-19 version 1.0, specifically in the /login.php file. The vulnerability arises because the application improperly handles the 'username' parameter, allowing attackers to inject malicious SQL code. This happens due to inadequate validation and sanitization of user input, enabling attackers to manipulate SQL queries executed by the system. Exploitation can be done remotely without authentication, making it easy for attackers to gain unauthorized access to the database and perform malicious actions. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, and potential full system compromise. Attackers can exploit the flaw to manipulate SQL queries, leading to data tampering, service disruption, and loss of data integrity and confidentiality. Since the attack can be performed remotely without authentication, it poses a high risk to the affected system's security and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the /login.php endpoint for injection flaws in the 'username' parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target.com/stc-log-keeper/login.php" --data="username=admin&password=any" -p username --batch. Additionally, manual testing with payloads such as 'admin' OR 1=1-- or time-based injections using sleep functions can help identify the flaw. Google dorking with queries like inurl:login.php can help identify vulnerable targets on your network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameterized queries to prevent SQL injection. 2) Apply strict input validation and sanitization on the 'username' parameter to ensure only expected input is accepted. 3) Minimize database user privileges by avoiding use of high-privilege accounts for application database access. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities. If possible, replace the affected product with a secure alternative as no known countermeasures are documented. [3, 2]