Quick answers
- Is CVE-2026-104609 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104609 being exploited in the wild.
- How severe is CVE-2026-104609?
- High severity, with a CVSS score of 7.3, published 2 October 2026.
- Which products and versions are affected?
- Onetwothreeneth HospitalManagementSystem up to commit 9ef91ed6007314b6473110ed699dff76d158f61d.
- Is there a fix for CVE-2026-104609?
- 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-104609 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104609?
- Check whether you run Onetwothreeneth HospitalManagementSystem 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.
Technical details
The application embeds unsanitized GET parameters (user_id, patient_id, physician_id, discounts_id, services_id) directly into SQL WHERE clauses across five edit pages without escaping or prepared statements. An unauthenticated attacker can leverage time-based blind SQL injection (e.g., ' AND SLEEP(1)-- -) via HTTP GET requests to extract the entire database, confirmed across all five vulnerable endpoints (edit_accounts.php, edit_patient.php, edit_physicians.php, edit_discounts.php, edit_services.php).
Affected products
- onetwothreeneth HospitalManagementSystem up to commit 9ef91ed6007314b6473110ed699dff76d158f61d
Timeline
- 2026-10-02: disclosed
- 2026-09-06: exploited: exploit made available to public; reported via GitHub issue