/

CVE-2026-90701

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Online Clinic listdoctor.php

CVE-2026-90701

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Confidentiality, Integrity, and Availability

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A SQL injection vulnerability in the online clinic management system allows attacker-controlled search text to influence database queries handled by listdoctor.php. If the endpoint is reachable and input is incorporated into SQL without adequate parameterization, a remote attacker may read, alter, or otherwise affect database operations.

Affected context

The issue occurs in deployments of the online-clinic-management-system that expose the listdoctor.php functionality and process the searchtext argument through database queries. Risk depends on whether the endpoint is remotely reachable, whether the input reaches a query-building path without effective controls, and what database permissions are available to the application.

Exploit preconditions

  • Attack surface: The remotely accessible listdoctor.php endpoint - Required access: Access to submit requests containing the searchtext argument;

authentication requirements depend on the deployment

  • Trigger point: Server-side processing of searchtext during doctor-list

searches

  • Why exploitation is possible: Input may influence SQL statement structure

when queries are constructed without reliable parameter binding or equivalent

safeguards

Why this happens

The underlying bug is an injection flaw in which externally supplied search data is treated as part of a database command rather than exclusively as data. This behavior maps primarily to CWE-89, SQL Injection, and more broadly to CWE-74, Improper Neutralization of Special Elements in an Input Used in a Command or API. The insecure pattern is dynamic SQL construction with insufficient separation between query code and user-controlled values.

Potential impact

  • An attacker may retrieve sensitive clinical or administrative records.
  • An attacker could modify or delete database information.
  • Database availability may be disrupted through resource-intensive queries.
  • Exposed database privileges could enable access to other application data.
  • Stolen information may support further attacks against users or connected systems.

General mitigation guidance

Mitigation generally focuses on preserving a strict separation between SQL statements and user-controlled values. Common defensive patterns include parameterized queries or prepared statements, narrowly scoped database accounts, and allowlisted search semantics where appropriate. Input validation should complement rather than replace query parameterization, while database error details should not be exposed to clients. Limiting endpoint exposure, applying least privilege, and protecting sensitive records with layered authorization controls can reduce the consequences of residual flaws.

How teams detect issues like this

Detection approaches include static analysis for string concatenation or interpolation used in database queries, review of all searchtext data flows, and code review checks requiring parameterized query APIs. Runtime monitoring can identify abnormal search requests, database errors, unexpected query shapes, and access patterns involving unusually broad result sets. Web application firewalls and database activity monitoring may provide policy enforcement and alerting, while automated security review tools can help flag injection-prone code paths.

Sources

SourceLink
github.comgithub.com/subhajitkhan/online-clinic-management-system/
github.comgithub.com/subhajitkhan/online-clinic-management-system/issues/2
vuldb.comvuldb.com/cve/CVE-2026-90701
vuldb.comvuldb.com/submit/916306
vuldb.comvuldb.com/vuln/403234
vuldb.comvuldb.com/vuln/403234/cti

Frequently asked

questions

It may be remotely exploitable when listdoctor.php is reachable over the

network and the searchtext value reaches an unsafe database query path.

Authentication and other access controls can limit the applicable scope.

The attacker needs to submit requests to the affected functionality. Whether

a valid account, session, or additional authorization is required depends on

how the application is deployed.

Use parameterized queries or prepared statements for every database operation,

keeping query structure separate from user-provided values. Apply least

privilege to the application's database account as an additional safeguard.

Establish secure database-access patterns, review input-to-query data flows,

enforce static analysis and code-review policies, and monitor application and

database activity for anomalous behavior.

Find out what's already
exploitable in your codebase.