# CVE-2024-52951: Cross-site scripting in n/a

> An authenticated attacker can execute arbitrary code in a victim's browser via stored XSS in the Access Request History of Omada Identity.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 27 Nov 2024
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-296f-9hr7-4mwq

## What is CVE-2024-52951?

CVE-2024-52951 is a high-severity cross-site scripting vulnerability in n/a, published on 27 Nov 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

Stored Cross-Site Scripting in the Access Request History in Omada Identity before version 15 update 1 allows an authenticated attacker to execute arbitrary code in the browser of a victim via a specially crafted link or by viewing a manipulated Access Request History

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-52951 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52951 is a high-severity cross-site scripting vulnerability in n/a, published on 27 Nov 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-52951 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-52951/ (Markdown: https://insights.sbomify.com/CVE-2024-52951/index.md)
```

## Sources

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

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