CVE-2026-2134
SQL Injection in PHPGurukul HMS manage-doctors.php Remote Exploit
Publication date: 2026-02-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 | 4.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the SQL injection point in the `id` parameter of the `/hms/admin/manage-doctors.php` file, specifically when the `del` parameter is used. A common detection method is to inject a time-based blind SQL injection payload and observe if the server response is delayed.'}, {'type': 'list_item', 'content': "Use a crafted URL like: http://target-site.com/hms/admin/manage-doctors.php?del=delete&id=1' AND (SELECT 6236 FROM (SELECT(SLEEP(5)))yZvQ)-- -"}, {'type': 'list_item', 'content': 'If the server response is delayed by approximately 5 seconds, it confirms the presence of the SQL injection vulnerability.'}, {'type': 'list_item', 'content': 'Steps to reproduce detection include: logging in as an administrator, navigating to the Manage Doctors page, intercepting the delete request with a tool like Burp Suite, modifying the `id` parameter with the payload, and sending the request.'}] [1]
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2134 is a critical SQL Injection vulnerability in PHPGurukul Hospital Management System version 4.0, specifically in the file /hms/admin/manage-doctors.php.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the 'id' parameter, triggered via the 'del' action, is directly concatenated into a SQL DELETE query without any input sanitization or use of prepared statements."}, {'type': 'paragraph', 'content': 'This allows an authenticated remote attacker to inject malicious SQL code, enabling them to execute arbitrary SQL commands on the database.'}, {'type': 'paragraph', 'content': 'The vulnerability is a time-based blind SQL injection, which can be confirmed by injecting payloads that cause delayed server responses.'}] [1, 2, 3]
How can this vulnerability impact me? :
Successful exploitation of this vulnerability can lead to unauthorized manipulation of the database.
- Deletion of data
- Disclosure of sensitive information
- Potential full system compromise
Because the vulnerability allows execution of arbitrary SQL commands remotely, it poses a significant risk to the confidentiality, integrity, and availability of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or official patches have been published for this vulnerability. Immediate mitigation steps include avoiding use of the affected component or replacing it with an alternative product.
Additionally, restricting access to the affected administrative interface and monitoring for suspicious activity can help reduce risk until a fix is available.
Implementing input validation and using prepared statements or parameterized queries in the code would be the proper long-term fix, but this requires code changes by the vendor or maintainers.