CVE-2026-7632
SQL Injection in Online Hospital Management System 1.0
Publication date: 2026-05-02
Last updated on: 2026-05-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | online_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?
This vulnerability exists in the Online Hospital Management System 1.0, specifically in the /viewappointment.php file. It involves manipulation of the 'delid' argument, which leads to an SQL injection vulnerability. This means an attacker can remotely inject malicious SQL code through this parameter.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection attacks, which can lead to unauthorized access, modification, or deletion of data within the system's database. This can compromise the integrity, confidentiality, and availability of sensitive information managed by the hospital system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL Injection vulnerability in the Online Hospital Management System allows unauthenticated remote attackers to delete appointment records and extract sensitive database information, including admin credentials. This can lead to unauthorized access and manipulation of sensitive personal and health-related data.
Such unauthorized access and data manipulation can result in violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and health information against unauthorized access, alteration, and deletion.
Failure to secure the system against this vulnerability could lead to non-compliance with these standards, potentially resulting in legal penalties, loss of trust, and harm to affected individuals.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `delid` parameter in the URL of the `viewappointment.php` file for SQL injection. Since the parameter is directly concatenated into a SQL query without sanitization, sending specially crafted input can reveal the vulnerability.
- Use curl or a web browser to send requests with SQL injection payloads to the `viewappointment.php` endpoint, for example: `curl "http://target/viewappointment.php?delid=1' OR '1'='1"`.
- Observe if the response indicates deletion of records or errors related to SQL syntax, which suggests SQL injection.
- Perform time-based blind SQL injection tests by injecting payloads that cause delays, such as `delid=1' AND SLEEP(5)--` and measuring response times.
- Monitor network traffic for unusual HTTP GET requests to `viewappointment.php` with suspicious `delid` parameter values.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements or parameterized queries to prevent SQL injection instead of directly concatenating user input.
- Add authentication and authorization checks before allowing deletion or modification of appointment records.
- Validate that the user owns the resource they are attempting to delete or modify.
- Change the HTTP method for state-changing operations from GET to POST to reduce risk of unintended or malicious requests.