Quick answers
- Is CVE-2026-90805 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90805 being exploited in the wild.
- How severe is CVE-2026-90805?
- High severity, with a CVSS score of 7.3, published 14 September 2026.
- Which products and versions are affected?
- subhajitkhan Online-Clinic-Management-System up to commit e9ee77a8827a1446220fa07ee693dc4d9a29a578.
- Is there a fix for CVE-2026-90805?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-90805 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-90805?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic SQL injection flaw in the doctor login module (doctorlogin.php). The vulnerable code directly concatenates unsanitized POST parameters (doc_mail and doc_pswd) into a SQL SELECT query without using prepared statements or input validation. An unauthenticated attacker can craft a malicious email address (e.g., "doctor@example.test' AND '1'='1' -- ") that bypasses the password check and returns a valid doctor record, establishing a session. The injected payload persists in the session and is used again in doctorhome.php, allowing full access to the doctor portal without authentication. No authentication or special privileges are required to exploit this vulnerability; a remote attacker only needs to know a doctor's email address. The project uses a rolling release model and has not yet responded to the early disclosure report.
Affected products
- subhajitkhan Online-Clinic-Management-System up to commit e9ee77a8827a1446220fa07ee693dc4d9a29a578
Timeline
- 2026-08-10: disclosed: Issue reported on GitHub
- 2026-09-14: advisory: Published on NVD as CVE-2026-90805