CVE-2025-6156
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-6156 is a critical SQL injection vulnerability in the PHPGurukul Nipah Virus Testing Management System version 1.0. It exists in the /bwdates-report-ds.php file, specifically involving the 'testtype' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. Exploiting this flaw enables attackers to manipulate SQL queries and perform unauthorized database operations remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive data, modification or deletion of records, full system control by attackers, and disruption of services. These consequences threaten system security and business continuity. [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 /bwdates-report-ds.php file for SQL injection. A proof-of-concept exploit uses a POST request with a payload that causes a time delay, confirming SQL injection. For example, you can use curl to send a POST request with a payload like: curl -X POST -d "mobilenumber=1234567890&testtype=1' and sleep(3) and '&birthdaytime=2023-09-30T10:50&submit=Submit" http://<target>/bwdates-report-ds.php. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:bwdates-report-ds.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats and block malicious data. 3) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Since no known countermeasures or patches are documented, it is also recommended to replace the affected software with an alternative product. [2, 3]