# Oqtane Framework Insecure Direct Object Reference vulnerability

Advisory record · `GHSA-2hr5-cvwp-jr5w`

- **Identifiers:** `GHSA-2hr5-cvwp-jr5w` · `CVE-2024-55186`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 20 Dec 2024
- **Updated:** 20 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Dec 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `Oqtane.Framework` (NuGet): affected `<=6.0.0`; no fixed version yet
- `Oqtane.Client` (NuGet): affected `<=6.0.0`; no fixed version yet
- `Oqtane.Server` (NuGet): affected `<=6.0.0`; no fixed version yet
- `Oqtane.Shared` (NuGet): affected `<=6.0.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Oqtane.Framework, Oqtane.Client, Oqtane.Server and Oqtane.Shared versions up to and including 6.0.0 are affected. A logged-in user can change the notification ID in a request URL to view inbox messages and mail details belonging to other users. No fix is listed.

Written 9 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:22 UTC: First seen by agentprime
- 31 Oct 2026, 15:22 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2hr5-cvwp-jr5w)

## Sources

- [GitHub Advisory Database: GHSA-2hr5-cvwp-jr5w](https://github.com/advisories/GHSA-2hr5-cvwp-jr5w)
- [OSV: GHSA-2hr5-cvwp-jr5w](https://osv.dev/vulnerability/GHSA-2hr5-cvwp-jr5w)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-55186>
- <https://github.com/oqtane/oqtane.framework/pull/4876/files>
- <https://gist.github.com/SmitShah1518/00de9ecc46c1a8e2b189185c9d92afb0>
- <https://github.com/oqtane/oqtane.framework>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2hr5-cvwp-jr5w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2hr5-cvwp-jr5w/>. Everything for agents: <https://agentprime.io/llms.txt>.