CVE-2025-6157
BaseFortify
Publication date: 2025-06-17
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-6157 is a critical SQL injection vulnerability in the PHPGurukul Nipah Virus Testing Management System version 1.0. It exists in the file /registered-user-testing.php, specifically in the handling of the 'testtype' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate SQL queries and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can manipulate SQL queries remotely without authentication, which impacts the confidentiality, integrity, and availability of the affected system. This can result in loss or corruption of sensitive data and disruption of services. [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 "testtype" parameter in the /registered-user-testing.php file for SQL injection. One method is to send crafted HTTP requests with SQL injection payloads, such as using a time delay payload like "sleep(5)" to observe response delays. For example, using curl to send a POST request with a payload: curl -X POST -d "testtype=1' OR SLEEP(5)-- " http://target/registered-user-testing.php. Additionally, searching for the vulnerable endpoint using Google dorking with the query "inurl:registered-user-testing.php" can help identify affected systems on your network or externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, rigorously validating and filtering all user inputs to ensure they conform to expected formats, and restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. If possible, replace the affected software with an alternative product. Applying these measures will reduce the risk of exploitation. [2, 3]