# CVE-2025-70063: Information disclosure in n/a

> An attacker can access other patients' confidential medical records by manipulating the viewid parameter in the Medical History module.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-8gfj-223w-87pr

## What is CVE-2025-70063?

CVE-2025-70063 is a medium-severity vulnerability in Phpgurukul Hospital Management System, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The 'Medical History' module in PHPGurukul Hospital Management System v4.0 contains an Insecure Direct Object Reference (IDOR) vulnerability. The application fails to verify that the requested 'viewid' parameter belongs to the currently authenticated patient. This allows a user to access the confidential medical records of other patients by iterating the 'viewid' integer.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-70063?

It affects 1 product.


Products: Phpgurukul Hospital Management System.

## How do I fix CVE-2025-70063?

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

## Is CVE-2025-70063 being exploited?

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

## Other vulnerabilities in Phpgurukul Hospital Management System

- [CVE-2025-56212](https://insights.sbomify.com/CVE-2025-56212/): SQL injection in n/a (critical 9.8)
- [CVE-2025-56214](https://insights.sbomify.com/CVE-2025-56214/): SQL injection in n/a (critical 9.8)
- [CVE-2024-51360](https://insights.sbomify.com/CVE-2024-51360/): Code injection in n/a (critical 9.8)
- [CVE-2020-26629](https://insights.sbomify.com/CVE-2020-26629/): File upload in n/a (critical 9.8)
- [CVE-2023-31498](https://insights.sbomify.com/CVE-2023-31498/): Privilege escalation in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70063 and fix it if it is affected.

What it is: CVE-2025-70063 is a medium-severity vulnerability in Phpgurukul Hospital Management System, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70063 exists.

Affected product: Phpgurukul Hospital Management System. 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-2025-70063/ (Markdown: https://insights.sbomify.com/CVE-2025-70063/index.md)
```

## Sources

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

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