CVE-2026-3980
SQL Injection in itsourcecode Online Doctor Appointment System
Publication date: 2026-03-12
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 |
|---|---|---|
| unguardable | online_doctor_appointment_system | 1.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
Can you explain this vulnerability to me?
CVE-2026-3980 is a critical SQL injection vulnerability found in version 1.0 of the itsourcecode Online Doctor Appointment System, specifically in the file /admin/patient_action.php.
The vulnerability arises from improper handling of the patient_id parameter, which is used directly in SQL queries without adequate input validation or sanitization.
This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized database access.
Various SQL injection techniques such as boolean-based blind, stacked queries, time-based blind, and UNION-based queries can be used to exploit this vulnerability.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, resulting in data leakage, modification, or deletion.
Attackers may gain full system compromise or cause service disruption.
The vulnerability impacts the confidentiality, integrity, and availability of the system.
Since the attack can be launched remotely without authentication, it is highly accessible to attackers.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
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 patient_id parameter in the /admin/patient_action.php file for SQL injection using various payloads.'}, {'type': 'list_item', 'content': "Boolean-based blind payload example: patient_id=5' AND 4751=4751 AND 'Jrza'='Jrza&action=fetch_single"}, {'type': 'list_item', 'content': "Stacked queries payload example: patient_id=5';SELECT SLEEP(5) # &action=fetch_single"}, {'type': 'list_item', 'content': "Time-based blind payload example: patient_id=5' AND (SELECT 4529 FROM (SELECT(SLEEP(5)))wNgU) AND 'FgHu'='FgHu&action=fetch_single"}, {'type': 'list_item', 'content': "UNION query payload example: patient_id=5' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x7176627671,0x596557456f634342796a714e555668584b4c4150735351686845706e53614b73444f79644e434944,0x7162787171),NULL,NULL,NULL,NULL-- -&action=fetch_single"}, {'type': 'paragraph', 'content': 'You can use tools like sqlmap to automate detection and exploitation attempts against the patient_id parameter to confirm the vulnerability.'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google Dorking with the query: inurl:admin/patient_action.php'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for routine operations.
- Conduct regular security audits to detect and address vulnerabilities promptly.
If possible, replace the affected software with an alternative product as no known countermeasures or mitigations have been documented.