# CVE-2026-115537: gedelumbung HospitalManagement URL Validation routing_pages.php simpan redirect


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-f7hr-g7fq-7xw6

## What is CVE-2026-115537?

CVE-2026-115537 is a medium-severity vulnerability in gedelumbung HospitalManagement, published on 23 Oct 2026. 

### Official description

A weakness has been identified in gedelumbung HospitalManagement up to c2d45543789a3887067d3915f69d44cfc2cf76a8. This affects the function simpan of the file application/modules/admin/controllers/routing_pages.php of the component URL Validation. This manipulation of the argument url_route causes open redirect. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-115537?


## How do I fix CVE-2026-115537?

No fix has been published for CVE-2026-115537 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115537 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115537 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115537 and fix it if it is affected.

What it is: CVE-2026-115537 is a medium-severity vulnerability in gedelumbung HospitalManagement, published on 23 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115537 exists.

Affected product: gedelumbung HospitalManagement. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115537/ (Markdown: https://insights.sbomify.com/CVE-2026-115537/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115537
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115537
- OSV: https://osv.dev/vulnerability/CVE-2026-115537

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115537/
Summaries are generated and may contain mistakes; the official description above is the record.