# CVE-2025-44595: Cross-site scripting in n/a

> Attackers can inject malicious scripts into Halo blog archives, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-mx5p-m7gp-h79c

## What is CVE-2025-44595?

CVE-2025-44595 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Halo v2.20.17 and before is vulnerable to Cross Site Scripting (XSS) in /halo_host/archives/{name}.

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

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

It affects 1 product.


Products: Halo Halo.

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

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

## Is CVE-2025-44595 being exploited?

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

## 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-44595 and fix it if it is affected.

What it is: CVE-2025-44595 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-44595 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-2025-44595/ (Markdown: https://insights.sbomify.com/CVE-2025-44595/index.md)
```

## Sources

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

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