CVE-2026-37601
SQL Injection in Patient Appointment Scheduler Admin Module
Publication date: 2026-04-14
Last updated on: 2026-04-14
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sourcecodester | patient_appointment_scheduler_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?
The Patient Appointment Scheduler System v1.0 by Sourcecodester has an SQL injection vulnerability in the file /scheduler/admin/appointments/manage_appointment.php.
This vulnerability exists in the 'id' parameter of the URL, which is used in SQL queries without proper sanitization.
An attacker can exploit this by injecting malicious SQL code, such as using a UNION-based SQL injection payload to extract sensitive information like the database name.
How can this vulnerability impact me? :
This SQL injection vulnerability allows an attacker to execute arbitrary SQL queries on the backend database.
As a result, an attacker could potentially leak sensitive data, manipulate or delete data, or further compromise the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL Injection vulnerability can be detected by testing the `id` parameter in the URL `/scheduler/admin/appointments/manage_appointment.php?id=` for SQL injection payloads.
A common detection method is to send a specially crafted HTTP request with a UNION-based SQL injection payload to see if the database responds with unexpected data.
- Example payload to test: `/scheduler/admin/appointments/manage_appointment.php?id=0' union select 1,2,3,database(),5,6--+`
- You can use command-line tools like curl to send this request and observe the response for database information leakage.
- Example curl command: `curl -i 'http://<target>/scheduler/admin/appointments/manage_appointment.php?id=0'%20union%20select%201,2,3,database(),5,6--+`
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Patient Appointment Scheduler System v1.0 allows attackers to execute arbitrary SQL queries, potentially leading to data leakage or further compromise of the system.
Such unauthorized access or exposure of sensitive patient data could result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and health information.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in the Patient Appointment Scheduler System v1.0, immediate steps include:
- Avoid using the vulnerable parameter `id` in `/scheduler/admin/appointments/manage_appointment.php` until a fix is applied.
- Implement input validation and parameterized queries or prepared statements to prevent SQL injection.
- Restrict access to the affected URL and ensure that only authorized users with proper privileges can access the administration pages.
- Change or secure the default login credentials (`admin/admin123`) to prevent unauthorized access.
- Monitor logs for suspicious activity related to SQL injection attempts.