# CVE-2024-28320: Missing authorization in n/a

> Attackers can manipulate user parameters to access and modify unauthorized patient data via crafted POST requests.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9w2p-xfp4-ggc4

## What is CVE-2024-28320?

CVE-2024-28320 is a high-severity missing authorization vulnerability in n/a, published on 29 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Insecure Direct Object References (IDOR) vulnerability in Hospital Management System 1.0 allows attackers to manipulate user parameters for unauthorized access and modifications via crafted POST request to /patient/edit-user.php.

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

## Which versions are affected by CVE-2024-28320?

It affects 1 product.


Products: Mayurik Hospital Management System.

## How do I fix CVE-2024-28320?

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

## Is CVE-2024-28320 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-11102](https://insights.sbomify.com/CVE-2024-11102/): SourceCodester Hospital Management System edit-doc.php cross site scripting (medium 5.3)
- [CVE-2024-11073](https://insights.sbomify.com/CVE-2024-11073/): SourceCodester Hospital Management System delete-account.php improper authorization (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28320 and fix it if it is affected.

What it is: CVE-2024-28320 is a high-severity missing authorization vulnerability in n/a, published on 29 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28320 exists.

Affected product: n/a. 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-2024-28320/ (Markdown: https://insights.sbomify.com/CVE-2024-28320/index.md)
```

## Sources

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

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