Quick answers
- Is CVE-2026-112139 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112139 being exploited in the wild.
- How severe is CVE-2026-112139?
- High severity, with a CVSS score of 7.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-112139?
- No fixed version is recorded yet. Use parameterized statements with typed identifiers instead of string concatenation, require administrator authentication for all mutation operations, and implement CSRF tokens to prevent unauthorized state-changing requests. 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-112139 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-112139?
- 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
Use parameterized statements with typed identifiers instead of string concatenation, require administrator authentication for all mutation operations, and implement CSRF tokens to prevent unauthorized state-changing requests.
Technical details
SQL injection occurs in admindocview.php, adminappview.php, approve.php, and disadd.php where the docid and appid parameters are concatenated directly into DELETE and UPDATE SQL statements without sanitization or parameterized queries. The affected scripts lack authentication checks, allowing unauthenticated remote attackers to execute arbitrary SQL commands; proof-of-concept demonstrates bulk deletion of all doctor records using a SQL OR condition.
Affected products
- subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578
Timeline
- 2026-09-01: disclosed: Vulnerability report filed on GitHub issue #5
- 2026-10-19: advisory