# CVE-2025-48739: Server-side request forgery in TheHive

> Authenticated admins can exploit SSRF in TheHive to proxy requests to internal network resources, bypassing network restrictions.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:L/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-w62p-cm3c-7rfc

## What is CVE-2025-48739?

CVE-2025-48739 is a medium-severity server-side request forgery vulnerability in StrangeBee TheHive, published on 23 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability in StrangeBee TheHive 5.2.0 before 5.2.16, 5.3.0 before 5.3.11, 5.4.0 before 5.4.10, and 5.5.0 before 5.5.1 allows remote authenticated attackers with admin permissions (allowing them to access specific API endpoints) to manipulate URLs to direct requests to unexpected hosts or ports. This allows the attacker to use a TheHive server as a proxy to reach internal or otherwise restricted resources. This could be exploited to access other servers on the internal network.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-48739?


## How do I fix CVE-2025-48739?

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

## Is CVE-2025-48739 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48739 and fix it if it is affected.

What it is: CVE-2025-48739 is a medium-severity server-side request forgery vulnerability in StrangeBee TheHive, published on 23 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-48739 in the wild and no public exploit code.

Affected product: StrangeBee TheHive. 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-2025-48739/ (Markdown: https://insights.sbomify.com/CVE-2025-48739/index.md)
```

## Sources

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

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