CVE-2024-55186 json
Oqtane Framework Insecure Direct Object Reference vulnerability
published last yr. modified 4mo ago also GHSA-2hr5-cvwp-jr5w , EUVD-2024-3544
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
An IDOR (Insecure Direct Object Reference) vulnerability exists in oqtane Framework 6.0.0, allowing a logged-in user to access inbox messages of other users by manipulating the notification ID in the request URL. By changing the notification ID, an attacker can view sensitive mail details belonging to other users.
Patch / fix
- github.com/oqtane/oqtane.framework#4876 pull request
Is CVE-2024-55186 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- gist.github.com https://gist.github.com/SmitShah1518/00de9ecc46c1a8e2b189185c9d92afb0 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Oqtane.Framework | <=6.0.0 |
no fix listed |
| nuget | Oqtane.Client | <=6.0.0 |
no fix listed |
| nuget | Oqtane.Server | <=6.0.0 |
no fix listed |
| nuget | Oqtane.Shared | <=6.0.0 |
no fix listed |
Classification
References
Sources
- CVE List CVE-2024-55186
- GitHub Advisory GHSA-2hr5-cvwp-jr5w
- NVD CVE-2024-55186
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.