Quick answers
- Is CVE-2026-112092 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112092 being exploited in the wild.
- How severe is CVE-2026-112092?
- Medium severity, with a CVSS score of 4.3, published 19 October 2026.
- Which products and versions are affected?
- Subhajitkhan Online-Clinic-Management-System up to e9ee77a8827a1446220fa07ee693dc4d9a29a578.
- Is there a fix for CVE-2026-112092?
- No fixed version is recorded yet. Validate all profile fields server-side and encode every untrusted value for HTML context using htmlspecialchars($value, ENT_QUOTES, 'UTF-8') or equivalent in every location where doctor data is displayed. 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-112092 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-112092?
- Check whether you run Subhajitkhan Online-Clinic-Management-System at an affected version. 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.
How to fix
Validate all profile fields server-side and encode every untrusted value for HTML context using htmlspecialchars($value, ENT_QUOTES, 'UTF-8') or equivalent in every location where doctor data is displayed.
Technical details
Stored cross-site scripting (XSS) in the doctor registration module: the doctorregistration.php file inserts the doc_name parameter directly into the database without encoding, and listdoctor.php and admindocview.php echo it back as raw HTML. An unauthenticated attacker can register a malicious doctor account with JavaScript payload in the doc_name field, which executes when any user views the public doctor directory or an administrator reviews registrations.
Affected products
- subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578
Timeline
- 2026-10-19: disclosed
- 2026-10-02: other: Issue reported to maintainer on GitHub