CVE-2025-5694
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-5694 is a critical SQL injection vulnerability in the PHPGurukul Human Metapneumovirus Testing Management System version 1.0. It occurs in the /search-report-result.php file where the 'serachdata' parameter is used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code, manipulating the database queries arbitrarily. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability allows attackers to perform unauthorized database operations such as accessing sensitive data, modifying or deleting data, gaining full system control, and disrupting services. The attack can be launched remotely and is straightforward to execute, with public proof-of-concept exploits available. This compromises the confidentiality, integrity, and availability of the affected system. [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 parameter 'serachdata' in the /search-report-result.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/search-report-result.php" --data="serachdata=123&search=Search" --risk=3 --level=5 --batch. Additionally, manual testing with boolean-based blind and time-based blind SQL injection payloads can be performed, such as sending POST requests with payloads like 'serachdata=123%' AND 3960=3960 AND 'wkPf%'='wkPf' or 'serachdata=123%' AND (SELECT SLEEP(5)) AND 'iQjk%'='iQjk'. Also, Google dorking with 'inurl:search-report-result.php' can help identify vulnerable targets. [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 rigorous input validation and filtering on the 'serachdata' parameter to ensure inputs conform to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. These steps help protect system security and maintain data integrity. [2, 3]