CVE-2025-5859
BaseFortify
Publication date: 2025-06-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 |
|---|---|---|
| phpgurukul | nipah_virus_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-5859 is a critical SQL injection vulnerability in the PHPGurukul Nipah Virus Testing Management System version 1.0. It exists in the /test-details.php file, specifically through the 'assignto' parameter, which is used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, manipulating database queries arbitrarily and performing unauthorized operations such as data leakage, tampering, or full system control. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Because the attack can be launched remotely without authentication, it poses significant security and operational risks, compromising the confidentiality, integrity, and availability of the system and its data. [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 'assignto' parameter in the /test-details.php file for SQL injection. One method is to use time-based blind SQL injection payloads such as: assignto=Rahul' RLIKE SLEEP(5) AND 'MWDA'='MWDA-105202365&submit=Submit which causes a delay in the database response if vulnerable. Additionally, the sqlmap tool can be used to automate detection by targeting the 'assignto' parameter to enumerate databases. Vulnerable targets can also be identified using Google Dorking with the query: inurl:test-details.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering to ensure inputs conform to expected formats, and minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. If possible, replacing the affected software with an alternative product is recommended. These actions help prevent SQL injection exploitation and protect system security and data integrity. [2, 3]