# CVE-2025-44594: Server-side request forgery in n/a

> An attacker can exploit an SSRF vulnerability in Halo CMS to make unauthorized server-side requests, potentially accessing internal resources.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-m32r-7fmp-xpvf

## What is CVE-2025-44594?

CVE-2025-44594 is a critical server-side request forgery vulnerability in n/a, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

halo v2.20.17 and before is vulnerable to server-side request forgery (SSRF) in /apis/uc.api.storage.halo.run/v1alpha1/attachments/-/upload-from-url.

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

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

It affects 1 product.


Products: Halo Halo.

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

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

## Is CVE-2025-44594 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32994](https://insights.sbomify.com/CVE-2022-32994/): File upload in n/a (critical 9.8)
- [CVE-2022-32995](https://insights.sbomify.com/CVE-2022-32995/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-18980](https://insights.sbomify.com/CVE-2020-18980/): Code injection in n/a (critical 9.8)
- [CVE-2020-21522](https://insights.sbomify.com/CVE-2020-21522/): Path traversal in n/a (critical 9.8)
- [CVE-2020-21523](https://insights.sbomify.com/CVE-2020-21523/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44594 is a critical server-side request forgery vulnerability in n/a, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44594 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-2025-44594/ (Markdown: https://insights.sbomify.com/CVE-2025-44594/index.md)
```

## Sources

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

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