CVE-2025-5693
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anujk305 | human_metapneumovirus_\(hmpv\)_-_testing_management_system | 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-5693 is a critical SQL injection vulnerability in the PHPGurukul Human Metapneumovirus Testing Management System version 1.0, specifically in the file /bwdates-report-result.php. The vulnerability arises because the 'fromdate' and 'todate' parameters are improperly handled and directly incorporated into SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database by executing unauthorized commands such as extracting, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data tampering, and disruption of system availability. Attackers can execute arbitrary SQL commands remotely without authentication, potentially gaining full control over the database and affecting the confidentiality, integrity, and availability of the system. This can lead to business continuity issues and compromise of critical information. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameters 'fromdate' and 'todate' in the /bwdates-report-result.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/bwdates-report-result.php" --data="fromdate=2000-01-01&todate=2025-01-01" -p todate --batch. Additionally, manual testing with payloads such as a time-based blind SQL injection using MySQL's SLEEP function can be performed, e.g., sending POST data: fromdate=2000-01-01&todate=2025-01-01' AND (SELECT SLEEP(5))-- . Google Dorking can also help identify vulnerable targets using the query: inurl:bwdates-report-result.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying strict input validation and filtering on the 'fromdate' and 'todate' parameters to ensure they conform to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. Since no official countermeasures are published, these steps are critical to reduce risk. [2, 3]