# CVE-2024-5955: Cross-site scripting in ePO Onprem Sp1 Update4

> Remote authenticated attackers can inject arbitrary content via XSS in Trellix ePolicy Orchestrator, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 20 Dec 2024
- **Updated:** 20 Dec 2024
- **Also known as:** GHSA-9qq6-35mf-f783

## What is CVE-2024-5955?

CVE-2024-5955 is a medium-severity cross-site scripting vulnerability in Trellix ePO Onprem Sp1 Update4, published on 20 Dec 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

Cross-site scripting vulnerability in Trellix ePolicy Orchestrator prior to ePO 5.10 Service Pack 1 Update 3 allows a remote authenticated attacker to craft requests causing arbitrary content to be injected into the response when accessing the epolicy Orchestrator.

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

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


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

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

## Is CVE-2024-5955 being exploited?

There is no known exploitation of CVE-2024-5955 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5955 is a medium-severity cross-site scripting vulnerability in Trellix ePO Onprem Sp1 Update4, published on 20 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-5955 in the wild and no public exploit code.

Affected product: Trellix ePO Onprem Sp1 Update4. 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-5955/ (Markdown: https://insights.sbomify.com/CVE-2024-5955/index.md)
```

## Sources

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

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