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-105472 Overview
CVE-2026-105472 is a SQL injection vulnerability in the girishsaraf Online-Appointment-Booking-System project, affecting commits up to f427b4757128ca253d33d0cc4e87bbb9c999a4d5. The flaw resides in the Booking Handler component, specifically within book.php. Attackers can manipulate the Doctor or appointment arguments to inject arbitrary SQL statements. The project follows a rolling release model, so no fixed version identifier is available. A public exploit exists, and the maintainer has not responded to the issue report filed on GitHub. The vulnerability is classified under [CWE-74] (Improper Neutralization of Special Elements in Output Used by a Downstream Component).
Critical Impact
Remote attackers with low privileges can inject SQL commands through the booking workflow to read or modify database content without user interaction.
Affected Products
- girishsaraf/Online-Appointment-Booking-System (GitHub project)
- All commits up to and including f427b4757128ca253d33d0cc4e87bbb9c999a4d5
- Rolling release — no discrete affected version numbers published
Discovery Timeline
- 2026-10-06 - CVE-2026-105472 published to NVD
- 2026-10-06 - Last updated in NVD database
- Status - Project maintainer notified via GitHub issue tracker; no response at the time of publication
Technical Details for CVE-2026-105472
Vulnerability Analysis
The vulnerability is a SQL injection flaw in book.php, the file that processes appointment booking requests. User-supplied input passed through the Doctor and appointment parameters is concatenated into a SQL query without parameterization or sanitization. An authenticated attacker with low-level privileges can submit crafted parameter values that break out of the intended query context. This permits execution of attacker-controlled SQL statements against the backing database.
Because the application exposes the vulnerable endpoint over the network, exploitation requires no local access. The exploit has been disclosed publicly, lowering the barrier to opportunistic abuse. Impact is limited to confidentiality, integrity, and availability of the application database. The EPSS probability for this CVE is 0.2%, reflecting limited observed exploitation activity.
Root Cause
The root cause is improper neutralization of special elements in input used to construct SQL queries [CWE-74]. The book.php handler does not use prepared statements or input validation before incorporating the Doctor and appointment arguments into database queries.
Attack Vector
The attack vector is network-based. An attacker with a valid low-privilege account submits a crafted booking request containing SQL metacharacters in the Doctor or appointment parameters. The injected payload executes within the application's database session. No user interaction is required to trigger the flaw.
No verified exploit code is reproduced here. Refer to the VulDB entry for CVE-2026-105472 and the GitHub Issue Tracker #10 for additional context.
Detection Methods for CVE-2026-105472
Indicators of Compromise
- Unexpected SQL syntax (single quotes, UNION, SELECT, --, /*) in HTTP request parameters sent to book.php
- Database error messages returned to clients requesting /book.php
- Anomalous database query patterns originating from the web application service account
- Unusual read or modification activity against appointment or user tables
Detection Strategies
- Deploy web application firewall (WAF) rules that inspect POST and GET parameters sent to book.php for SQL injection patterns
- Enable database query logging and alert on queries referencing unexpected tables or using tautologies such as OR 1=1
- Review web server access logs for repeated requests to /book.php with suspicious parameter encodings
Monitoring Recommendations
- Baseline normal query volume and parameter structure for the Booking Handler, then alert on deviations
- Forward web server, application, and database logs to a centralized analytics platform for correlation
- Monitor authentication logs for low-privilege accounts generating unexpected database errors
How to Mitigate CVE-2026-105472
Immediate Actions Required
- Restrict network exposure of the application to trusted users until a fix is applied
- Place a WAF in front of the application with SQL injection signatures enabled for book.php
- Audit the book.php source and refactor affected queries to use parameterized statements
- Rotate database credentials if exploitation is suspected and review the database for unauthorized changes
Patch Information
No official patch is available. The project operates under a rolling release model, and the maintainer has not responded to the GitHub Issue Tracker #10 report. Organizations relying on this codebase should apply source-level fixes locally or migrate to a maintained alternative. Track status via the GitHub Project Repository and the VulDB CVE-2026-105472 advisory.
Workarounds
- Modify book.php to use prepared statements with bound parameters for the Doctor and appointment inputs
- Apply strict server-side input validation that rejects non-alphanumeric characters in these parameters
- Enforce least-privilege database accounts so the web application cannot alter schema or access unrelated tables
- Disable or remove the application from production until remediation is validated
# Example PHP remediation pattern (illustrative) for book.php
# Replace string-concatenated queries with prepared statements:
# $stmt = $pdo->prepare('INSERT INTO bookings (doctor, appointment) VALUES (:doctor, :appointment)');
# $stmt->execute([':doctor' => $_POST['Doctor'], ':appointment' => $_POST['appointment']]);
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

