Quick answers
- Is CVE-2026-102845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102845 being exploited in the wild.
- How severe is CVE-2026-102845?
- Medium severity, with a CVSS score of 5.3, published 30 September 2026.
- Which products and versions are affected?
- Gedelumbung HospitalManagement up to c2d45543789a3887067d3915f69d44cfc2cf76a8.
- Is there a fix for CVE-2026-102845?
- 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-102845 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-102845?
- Check whether you run Gedelumbung HospitalManagement 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 vulnerability exists in index.php where ENVIRONMENT is hardcoded to 'development' and error_reporting is set to E_ALL, combined with db_debug=TRUE in the database configuration. This causes verbose error messages containing internal file paths, SQL queries, and MySQL credentials to be leaked in HTTP responses. An unauthenticated remote attacker can trigger database errors (e.g., via SQL injection payloads) to obtain sensitive information with no preconditions beyond network access.
Affected products
- gedelumbung HospitalManagement up to c2d45543789a3887067d3915f69d44cfc2cf76a8
Timeline
- 2026-08-25: disclosed: Issue opened on GitHub
- 2026-09-30: advisory: Published on NVD as CVE-2026-102845