Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105387 Overview
CVE-2026-105387 is a SQL injection vulnerability in the girishsaraf Online-Appointment-Booking-System, a PHP-based web application. The flaw resides in the mysqli_query call within cover.php, part of the Patient Login Handler component. Attackers can manipulate the uname and psw parameters to inject arbitrary SQL statements. The project uses a rolling release model, so specific affected and fixed version numbers are not published. The upstream maintainer was notified through an issue report but has not responded. A public exploit is available, increasing the likelihood of opportunistic exploitation against exposed instances.
Critical Impact
Unauthenticated remote attackers can inject SQL through the login form, enabling authentication bypass, data disclosure, and potential modification of the backend database.
Affected Products
- girishsaraf Online-Appointment-Booking-System up to commit f427b4757128ca253d33d0cc4e87bbb9c999a4d5
- cover.php Patient Login Handler component
- Deployments using the rolling release distribution model from the upstream GitHub repository
Discovery Timeline
- 2026-10-05 - CVE-2026-105387 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-105387
Vulnerability Analysis
The vulnerability is a classic SQL injection categorized under [CWE-74] (Improper Neutralization of Special Elements in Output Used by a Downstream Component). The Patient Login Handler accepts uname and psw POST parameters and concatenates them into a SQL query executed via mysqli_query in cover.php. Because the inputs are not parameterized or sanitized, attacker-controlled strings alter the structure of the query. Successful exploitation yields limited confidentiality, integrity, and availability impact on the database. The exploit is public, which lowers the barrier for commodity attack frameworks and automated scanners to weaponize the issue.
Root Cause
The root cause is unsafe query construction. User-supplied credentials are inserted directly into a SQL string rather than passed through prepared statements or parameter binding. The absence of input validation, output encoding, and least-privilege database accounts compounds the exposure.
Attack Vector
The attack is remote and unauthenticated. An adversary submits crafted values in the uname or psw fields of the login form. Payloads such as single-quote terminators followed by boolean or UNION-based clauses can bypass authentication or extract records. No user interaction or elevated privileges are required. Refer to the VulDB entry for CVE-2026-105387 and the upstream GitHub issue for additional context.
// No verified exploit code is published in the enriched dataset.
// The vulnerable pattern is unsanitized concatenation of login parameters
// into a mysqli_query call inside cover.php within the Patient Login Handler.
Detection Methods for CVE-2026-105387
Indicators of Compromise
- Web server access logs containing SQL metacharacters such as ', --, #, UNION, or OR 1=1 in POST bodies targeting cover.php
- Unexpected successful logins without preceding account creation events
- Database error messages referencing mysqli syntax errors tied to the login endpoint
- Spikes in failed login traffic followed by anomalous query response sizes
Detection Strategies
- Deploy a web application firewall (WAF) ruleset tuned for SQL injection patterns on the /cover.php endpoint
- Enable MySQL general query logging temporarily to identify malformed statements originating from the login flow
- Correlate authentication events with source IP reputation and request-body entropy
Monitoring Recommendations
- Alert on repeated 500-series responses from cover.php indicating backend query failures
- Monitor outbound database traffic for abnormal row counts returned to the application tier
- Track access to sensitive patient tables outside of normal application workflows
How to Mitigate CVE-2026-105387
Immediate Actions Required
- Restrict public exposure of the Online-Appointment-Booking-System until a patched build is available
- Place the application behind a WAF with SQL injection signatures enabled in blocking mode
- Rotate database credentials and audit the MySQL account used by the application for excessive privileges
- Review authentication and database logs for signs of prior exploitation
Patch Information
The upstream project at the girishsaraf Online-Appointment-Booking-System repository has not released a fix as of the NVD publication date. Because the project follows a rolling release model, there are no numbered versions to pin to. Administrators should fork the repository and apply parameterized queries directly, or migrate to a maintained appointment-booking platform.
Workarounds
- Replace the mysqli_query call in cover.php with mysqli_prepare and bound parameters for uname and psw
- Enforce server-side input validation to reject non-alphanumeric characters in username fields
- Restrict the application's MySQL account to SELECT on only the required tables and remove FILE, GRANT, and administrative privileges
- Require network-level access controls (VPN or IP allowlist) in front of the login page
# Example hardening: restrict MySQL privileges for the application account
mysql -u root -p -e "REVOKE ALL PRIVILEGES ON *.* FROM 'appuser'@'%'; \
GRANT SELECT, INSERT, UPDATE ON appointment_db.* TO 'appuser'@'%'; \
FLUSH PRIVILEGES;"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

