CVE-2025-7176
BaseFortify
Publication date: 2025-07-08
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 | hospital_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-7176 is a critical SQL injection vulnerability in PHPGurukul Hospital Management System version 1.0, specifically in the file view-medhistory.php. The vulnerability arises because the 'viewid' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database to access, modify, or delete sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive patient data, data leakage, modification or deletion of critical information, and potentially full control over the system. It can also cause service disruptions. Since the exploit can be performed remotely without authentication, it poses a significant security risk to the confidentiality, integrity, and availability of the hospital management system's data and services. [1, 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 'viewid' parameter in the URL of the 'view-medhistory.php' file for SQL injection. One method is to use sqlmap, an automated SQL injection tool, targeting the vulnerable URL parameter. For example, a command like: sqlmap -u "http://target/view-medhistory.php?viewid=1" --batch can be used to test for SQL injection. Additionally, a proof-of-concept time-based blind SQL injection payload is: viewid=' AND (SELECT 6468 FROM (SELECT(SLEEP(5)))POHd) AND 'frgd'='frgd, which can be manually tested to observe delays indicating injection vulnerability. Vulnerable targets can also be identified using Google dorking with the query "inurl:view-medhistory.php" to find instances of the affected page. [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 limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. Additionally, conducting regular security audits of code and systems is recommended to detect and address vulnerabilities promptly. Since no known mitigations or countermeasures have been documented, replacing the affected component with an alternative product is also suggested. [2, 3, 1]