Quick answers
- Is CVE-2026-93532 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93532 being exploited in the wild.
- How severe is CVE-2026-93532?
- Medium severity, with a CVSS score of 6.3, published 18 September 2026.
- Which products and versions are affected?
- Gedelumbung HospitalManagement up to c2d45543789a3887067d3915f69d44cfc2cf76a8.
- Is there a fix for CVE-2026-93532?
- 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-93532 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93532?
- 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 password change and profile update handlers in application/modules/global/controllers/password.php and profil.php perform IDOR attacks by accepting user identifiers (kode_user, username) from POST parameters without validating they match the authenticated session. The password endpoint has a weak guard requiring knowledge of the victim's current password, but the profile endpoint has no such protection. CSRF protection is globally disabled, allowing cross-site request forgery. A fix exists but the project has not yet responded to the disclosure.
Affected products
- gedelumbung HospitalManagement up to c2d45543789a3887067d3915f69d44cfc2cf76a8
Timeline
- 2026-08-22: disclosed: Issue reported on GitHub
- 2026-09-18: advisory: CVE-2026-93532 published