# CVE-2024-55471: Oqtane Framework Insecure Direct Object Reference vulnerability

> Attackers can access sensitive user information by manipulating ID parameters in Oqtane Framework, requiring an upgrade to secure the application.

- **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:** 20 Dec 2024
- **Updated:** 20 Dec 2024
- **Also known as:** GHSA-hhcw-wwxv-g95c

## What is CVE-2024-55471?

CVE-2024-55471 is a medium-severity vulnerability in n/a, published on 20 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Oqtane Framework is vulnerable to Insecure Direct Object Reference (IDOR) in Oqtane.Controllers.UserController. This allows unauthorized users to access sensitive information of other users by manipulating the id parameter.

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

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

4 open source packages ship an affected version, including Oqtane.Framework and Oqtane.Server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Oqtane.Framework` | NuGet | All versions to 6.0.0 | None |
| `Oqtane.Framework` | NuGet | All versions to 6.0.0 | None |
| `Oqtane.Server` | NuGet | All versions to 6.0.0 | None |
| `Oqtane.Server` | NuGet | All versions to 6.0.0 | None |

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

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

## Is CVE-2024-55471 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-55471 is a medium-severity vulnerability in n/a, published on 20 Dec 2024. 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-2024-55471 exists.

Affected packages and fixed versions:
- Oqtane.Framework (NuGet): affected all versions up to 6.0.0; no fix listed
- Oqtane.Framework (NuGet): affected all versions up to 6.0.0; no fix listed
- Oqtane.Server (NuGet): affected all versions up to 6.0.0; no fix listed
- Oqtane.Server (NuGet): affected all versions up to 6.0.0; no fix listed

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-55471/ (Markdown: https://insights.sbomify.com/CVE-2024-55471/index.md)
```

## Sources

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

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