CVE-2026-37602
SQL Injection in SourceCodester Patient Scheduler User Management
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/user/manage_user.php.
This vulnerability occurs at the URL endpoint /scheduler/admin/?page=user/manage_user&id= where the id parameter is not properly sanitized, allowing an attacker to inject malicious SQL code.
An attacker can exploit this by sending specially crafted SQL queries through the id parameter, such as using a UNION-based SQL injection to retrieve sensitive information like the database name.
How can this vulnerability impact me? :
This SQL injection vulnerability allows an attacker to execute arbitrary SQL commands on the underlying database.
As a result, an attacker could gain unauthorized access to sensitive data stored in the scheduler_db database, manipulate or delete data, and potentially compromise the integrity and confidentiality of 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 sending crafted HTTP GET requests to the vulnerable endpoint and observing the response for SQL injection behavior.
Specifically, you can test the URL endpoint `/scheduler/admin/?page=user/manage_user&id=` by injecting SQL payloads into the `id` parameter.
An example command using curl to test the vulnerability is:
- curl "http://<target-host>/scheduler/admin/?page=user/manage_user&id=0' union select 1,database(),3,4,5,6,7,8,9,10--+" -H "User-Agent: Mozilla/5.0" -H "Accept: text/html"
If the response contains the database name (e.g., `scheduler_db`), it indicates the presence of the SQL injection vulnerability.
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 an attacker to execute arbitrary SQL commands, potentially leading to unauthorized data disclosure or manipulation within the scheduler_db database.
Such unauthorized access or data breaches can impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data. If exploited, this vulnerability could lead to exposure of protected health information or personal data, thereby violating these regulations.
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 unsanitized input directly in SQL queries, especially the `id` parameter in `/scheduler/admin/user/manage_user.php`.
- Implement prepared statements or parameterized queries to prevent injection attacks.
- Restrict database permissions to limit the impact of any potential injection.
- Consider temporarily restricting access to the vulnerable endpoint or applying web application firewall (WAF) rules to block suspicious input patterns.
- Change default or weak credentials such as `admin/admin123` to strong, unique passwords to reduce risk.
- Monitor logs for unusual activity targeting the vulnerable parameter.