CVE-2025-51044
BaseFortify
Publication date: 2025-07-29
Last updated on: 2025-08-07
Assigner: MITRE
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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-51044 is a critical SQL injection vulnerability in the Nipah virus (NiV) Testing Management System version 1.0, specifically in the /new-user-testing.php file. It occurs because the "govtissuedid" parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code, potentially gaining unauthorized access to the database, leaking or manipulating data, and compromising the entire system without needing to log in. [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive data, data leakage, data tampering, disruption of services, and potentially full system compromise. Attackers can exploit it without authentication, which poses severe threats to system security and business continuity. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /new-user-testing.php endpoint for SQL injection in the "govtissuedid" POST parameter. A common approach is to use sqlmap, an automated SQL injection tool, to confirm exploitability. For example, you can run a command like: sqlmap -u "http://target/new-user-testing.php" --data="govtissuedid=1" --risk=3 --level=5 --technique=T --dbms=mysql to test for time-based blind SQL injection using the MySQL SLEEP function. Additionally, manual testing can involve sending crafted POST requests with payloads that include SQL commands to observe abnormal delays or error messages. [1]
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 privileges by avoiding the use of high-privilege accounts (such as root or admin) for routine database operations. [1]