Skip to main content
Vulnerability Database/CVE-2026-105470

CVE-2026-105470: Appointment Booking System SQL Injection

CVE-2026-105470 is a SQL injection vulnerability in Online-Appointment-Booking-System affecting the Doctor Search endpoint. Attackers can exploit the doctorname parameter to execute malicious SQL queries. This article covers technical details, impact analysis, and mitigation strategies.

Published:

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-105470 Overview

CVE-2026-105470 is a SQL injection vulnerability in the girishsaraf Online-Appointment-Booking-System, affecting the project up to commit f427b4757128ca253d33d0cc4e87bbb9c999a4d5. The flaw resides in the mysqli_query call within locateus.php, part of the Doctor Search Endpoint. Attackers can manipulate the doctorname parameter to inject arbitrary SQL statements. The project follows a rolling-release model, so no versioned fix is available. The maintainer was notified via an issue report but has not responded. The exploit is publicly disclosed, enabling remote exploitation without authentication or user interaction.

Critical Impact

Unauthenticated remote attackers can inject SQL through the doctorname parameter in locateus.php, potentially reading or modifying database contents of the appointment booking system.

Affected Products

  • girishsaraf Online-Appointment-Booking-System up to commit f427b4757128ca253d33d0cc4e87bbb9c999a4d5
  • Component: Doctor Search Endpoint (locateus.php)
  • Function: mysqli_query with user-controlled doctorname argument

Discovery Timeline

  • 2026-10-05 - CVE-2026-105470 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-105470

Vulnerability Analysis

The vulnerability is a classic SQL injection flaw [CWE-74] in a PHP web application. The locateus.php script accepts a doctorname request parameter and concatenates it directly into a SQL statement passed to mysqli_query. Because the input is not parameterized or escaped, attackers can terminate the intended query and append arbitrary SQL. Exploitation requires only network access to the endpoint. No credentials or user interaction are needed. Public disclosure through VulDB and the project's GitHub issue tracker increases the likelihood of opportunistic exploitation against exposed instances.

Root Cause

The root cause is improper neutralization of special elements in a SQL query. The doctorname parameter from the HTTP request is passed into a dynamically assembled query string rather than bound to a prepared statement. PHP's mysqli extension supports parameterized queries through mysqli_prepare and bind_param, but these safeguards are absent in the vulnerable code path. Any single-quote, semicolon, or SQL keyword supplied by the attacker is interpreted as part of the query.

Attack Vector

An unauthenticated remote attacker sends a crafted HTTP request to the Doctor Search Endpoint, supplying a malicious value for the doctorname parameter. Payloads commonly use UNION SELECT constructs to exfiltrate rows from other tables, boolean-based blind techniques to infer values, or time-based payloads such as SLEEP() when output is suppressed. Successful exploitation can expose patient records, doctor credentials, and appointment data, and may allow modification of the underlying database depending on the privileges of the database user.

See the VulDB entry for CVE-2026-105470 and GitHub Issue #8 for additional technical context.

Detection Methods for CVE-2026-105470

Indicators of Compromise

  • HTTP requests to locateus.php containing SQL metacharacters in the doctorname parameter, such as single quotes, --, UNION, SELECT, or SLEEP(.
  • Unexpected database errors in PHP or web server logs referencing mysqli_query or syntax errors tied to the Doctor Search Endpoint.
  • Anomalous outbound data volumes or long-running database queries originating from the application's database user.

Detection Strategies

  • Deploy Web Application Firewall (WAF) rules that flag SQL injection patterns targeting the doctorname query parameter.
  • Enable database query logging and alert on queries that reference unexpected tables or use UNION, INFORMATION_SCHEMA, or BENCHMARK/SLEEP constructs.
  • Review application and reverse-proxy access logs for repeated probes of locateus.php from the same source address.

Monitoring Recommendations

  • Forward web server, PHP error, and MySQL general query logs to a centralized analytics platform for correlation.
  • Baseline normal query volume to the appointment database and alert on sudden spikes or errors.
  • Monitor for post-exploitation behavior such as new administrative accounts, unexpected file writes to the web root, or credential dumps.

How to Mitigate CVE-2026-105470

Immediate Actions Required

  • Restrict public access to the application until mitigations are in place, especially if it holds patient or appointment data.
  • Place the application behind a WAF with SQL injection signatures enabled and block requests containing suspicious doctorname payloads.
  • Rotate database credentials and audit the database user's privileges, enforcing least privilege on the account used by the application.

Patch Information

No official patch is available. The maintainer of the girishsaraf Online-Appointment-Booking-System repository has not responded to the disclosure recorded in GitHub Issue #8. Operators running this project should apply source-level fixes themselves by replacing the vulnerable mysqli_query call in locateus.php with a prepared statement that binds the doctorname parameter.

Workarounds

  • Modify locateus.php to use mysqli_prepare with bind_param, treating doctorname as a bound string parameter rather than concatenating it into the query.
  • Add server-side input validation that rejects doctorname values containing SQL metacharacters or exceeding expected length.
  • If source modification is not possible, remove or disable the Doctor Search Endpoint until a patched version is deployed.
bash
# Example WAF rule (ModSecurity) blocking SQLi patterns in doctorname
SecRule ARGS:doctorname "@rx (?i)(union(\s|/\*.*\*/)+select|sleep\s*\(|benchmark\s*\(|--|;|')" \
  "id:1052026105470,phase:2,deny,status:403,log,\
  msg:'Possible SQL injection against locateus.php (CVE-2026-105470)'"

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.