CVE-2026-5180
SQL Injection in Simple Doctors Appointment System Admin Login
Publication date: 2026-03-31
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 |
|---|---|---|
| sourcecodester | simple_doctors_appointment_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
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, alter or delete records, and potentially take full control of the affected system.
Since the attack can be performed remotely without authentication, it significantly increases the risk of data breaches and system compromise.
Can you explain this vulnerability to me?
CVE-2026-5180 is a critical SQL injection vulnerability found in the Simple Doctor's Appointment System version 1.0, specifically in the '/admin/ajax.php?action=login2' file. The flaw occurs because the 'email' parameter used during the login process is not properly validated or sanitized before being included in SQL queries.
This improper handling allows attackers to inject malicious SQL code remotely without needing to authenticate, potentially enabling them to access, modify, or delete sensitive data in the database.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The CVE-2026-5180 vulnerability can be detected by testing the 'email' parameter in the POST request to the '/admin/ajax.php?action=login2' endpoint for SQL injection flaws.
Tools like sqlmap can be used to automate detection by targeting the 'email' parameter with time-based and boolean-based blind SQL injection techniques.
- Use sqlmap with a command similar to: sqlmap -u "http://targetsite/admin/ajax.php?action=login2" --data="[email protected]&password=test" -p email --technique=BEUSTQ
- Manually test by sending crafted POST requests to the vulnerable endpoint with SQL injection payloads in the 'email' parameter to observe abnormal responses or delays.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
Enforce strict input validation and filtering on the 'email' parameter to ensure inputs conform to expected formats.
Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations.
Conduct regular security audits to detect and address vulnerabilities promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Simple Doctors Appointment System allows attackers to gain unauthorized access to sensitive data, modify or delete records, and potentially take full control of the system. Such unauthorized access and data manipulation can lead to breaches of personal and health-related information.
This kind of security flaw can result in non-compliance with common standards and regulations such as GDPR and HIPAA, which require the protection of personal and health information against unauthorized access and data breaches.
Failure to protect sensitive data due to this vulnerability could lead to legal and regulatory consequences, including fines and reputational damage.