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

> Attackers can access sensitive medical records by manipulating the ID parameter in the URL, exposing patient data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-257p-qfc7-7ff5

## What is CVE-2024-23747?

CVE-2024-23747 is a high-severity missing authorization vulnerability in n/a, published on 29 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Moderna Sistemas ModernaNet Hospital Management System 2024 is susceptible to an Insecure Direct Object Reference (IDOR) vulnerability. This vulnerability resides in the system's handling of user data access through a /Modernanet/LAUDO/LAU0000100/Laudo?id= URI. By manipulating this id parameter, an attacker can gain access to sensitive medical information.

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

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

It affects 1 product.


Products: Modernasistemas Modernanet Hospital Management System 2024.

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

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

## Is CVE-2024-23747 being exploited?

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

Public exploit code:

- Moderna Sistemas ModernaNet Hospital Management System 2024 is susceptible to an Insecure Direct Object Reference (IDOR) vulnerability (github_poc): https://github.com/louiselalanne/CVE-2024-23747

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23747 is a high-severity missing authorization vulnerability in n/a, published on 29 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23747 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-23747/ (Markdown: https://insights.sbomify.com/CVE-2024-23747/index.md)
```

## Sources

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

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