CVE-2026-90701

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability was detected in subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578. The affected element is an unknown function of the file listdoctor.php. Performing a manipulation of the argument searchtext results in sql injection. The attack may be initiated remotely. The exploit is now public and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
64(Attend)
EG Risk 64/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
No patch confirmed yet.
generic

GitHub - subhajitkhan/online-clinic-management-system: Aim of this project is to develop a dynamic web based application using PHP, HTML, CSS,Bootstrap, JavaScript,Jquery, and MySQL to provide appointment to the patients according to doctors’ availability. The main three modules in our project are Patient module, Doctor Module and Admin module. Patients have to register themselves so that they can login into our system. Then patient can select department as well as doctor according to their ch...

GitHub - subhajitkhan/online-clinic-management-system: Aim of this project is to develop a dynamic web based application using PHP, HTML, CSS,Bootstrap, JavaScript,Jquery, and MySQL to provide appointment to the patients according to doctors’ availability. The main three modules in our project are Patient module, Doctor Module and Admin module. Patients have to register themselves so that they can login into our system. Then patient can select department as well as doctor according to their choice. If the doctor is free at that day, patient will get appointment. Patient can also cancel appointment. Similarly doctors can also register themselves and have to wait for admin’s approval. After that they can see their appointments, patient’s details etc. Admins have to register themselves explicitly through database. After login admins can approve doctor’s availability or unavailability and also can view appointments, doctors list, feedback and reports. The USP of our project is, patients can chat with respective doctors. · GitHub

https://github.com/subhajitkhan/online-clinic-management-system/
generic

SQL injection in the public doctor directory discloses administrator credentials · Issue #2 · subhajitkhan/online-clinic-management-system · GitHub

https://github.com/subhajitkhan/online-clinic-management-system/issues/2

Vendor Advisories for CVE-2026-90701(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 09:40 UTCGHSA enrichment
  2. 2026-09-24 21:42 UTCEG score recompute
  3. 2026-09-24 21:42 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 08:53 UTCGHSA enrichment
  6. 2026-09-23 20:56 UTCEG score recompute
  7. 2026-09-23 20:56 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 09:00 UTCGHSA enrichment
  10. 2026-09-22 21:03 UTCEG score recompute
  11. 2026-09-22 21:03 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 09:07 UTCEG score recompute
  14. 2026-09-22 09:06 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 21:00 UTCGHSA enrichment
  17. 2026-09-21 09:03 UTCGHSA enrichment
  18. 2026-09-20 21:07 UTCEG score recompute
  19. 2026-09-20 21:06 UTCGHSA enrichment
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 09:09 UTCGHSA enrichment
  22. 2026-09-19 21:12 UTCEG score recompute
  23. 2026-09-19 21:12 UTCGHSA enrichment
  24. 2026-09-19 09:13 UTCGHSA enrichment
  25. 2026-09-18 21:16 UTCEG score recompute
Show 26 more
  1. 2026-09-18 21:16 UTCGHSA enrichment
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 09:03 UTCGHSA enrichment
  4. 2026-09-17 21:06 UTCEG score recompute
  5. 2026-09-17 21:06 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 09:09 UTCGHSA enrichment
  8. 2026-09-16 21:12 UTCEG score recompute
  9. 2026-09-16 21:12 UTCGHSA enrichment
  10. 2026-09-16 14:09 UTCEPSS rescore
  11. 2026-09-16 08:55 UTCEG score recompute
  12. 2026-09-16 08:55 UTCGHSA enrichment
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 20:58 UTCGHSA enrichment
  15. 2026-09-15 09:01 UTCGHSA enrichment
  16. 2026-09-14 21:05 UTCGHSA enrichment
  17. 2026-09-14 15:21 UTCEG score recompute
  18. 2026-09-14 15:21 UTCGHSA enrichment
  19. 2026-09-14 15:21 UTCNVD updateCVSS v4 → 5.5
  20. 2026-09-14 14:40 UTCEG score recompute
  21. 2026-09-14 14:40 UTCGHSA enrichment
  22. 2026-09-14 14:39 UTCMITRE cvelistV5CVSS v4 → 6.9
  23. 2026-09-14 10:21 UTCEG score recompute
  24. 2026-09-14 10:20 UTCNVD updateCVSS v4 → 5.5
  25. 2026-09-14 09:30 UTCEG score recompute
  26. 2026-09-14 09:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90701?
CVE-2026-90701 is a high vulnerability published on September 14, 2026. A vulnerability was detected in subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578. The affected element is an unknown function of the file listdoctor.php. Performing a manipulation of the argument searchtext results in sql injection. The attack may be…
When was CVE-2026-90701 disclosed?
CVE-2026-90701 was first published in the National Vulnerability Database on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90701 actively exploited?
CVE-2026-90701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.4% of all scored CVEs.
What is the CVSS score of CVE-2026-90701?
CVE-2026-90701 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-90701?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90701, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-90701

Explore →

Is Your Infrastructure Affected by CVE-2026-90701?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.