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

> Attackers can inject malicious JavaScript into TheHive case reports, leading to code execution in the victim's browser context.

- **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:** 19 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-75rf-h4vm-w82h

## What is CVE-2024-22877?

CVE-2024-22877 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Jan 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

StrangeBee TheHive 5.2.0 to 5.2.8 is vulnerable to Cross Site Scripting (XSS) in the case reporting functionality. This feature allows an attacker to insert malicious JavaScript code inside the template or its variables, that will be executed in the context of the TheHive application when the HTML report is opened.

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

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

It affects 1 product.


Products: Strangebee Thehive.

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

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

## Is CVE-2024-22877 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-18376](https://insights.sbomify.com/CVE-2017-18376/): Privilege escalation in n/a (high 8.8)
- [CVE-2026-63098](https://insights.sbomify.com/CVE-2026-63098/): TheHive 4.1.24 Unauthenticated Information Disclosure via /api/status Endpoint (medium 6.9)
- [CVE-2024-22876](https://insights.sbomify.com/CVE-2024-22876/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22877 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Jan 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-22877 in the wild and no public exploit code.

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

## Sources

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

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