# CVE-2025-40846: HaloITSM open redirect via the returnUrl

> Attackers can redirect users to malicious sites or inject JavaScript via the returnUrl parameter in HaloITSM Account Security Settings.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:L/VA:N/SC:H/SI:H/SA:H/S:P/AU:Y/R:U/RE:L/U:Red`)
- **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:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-mcvh-54mc-g3gg

## What is CVE-2025-40846?

CVE-2025-40846 is a high-severity vulnerability in HaloITSM ITSM, published on 8 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Input Validation, the returnUrl parameter in Account Security Settings lacks proper input validation, allowing attackers to redirect users to malicious websites (Open Redirect) and inject JavaScript code to perform cross site scripting attack.

The vulnerability affects Halo versions up to 2.174.101 and all versions between 2.175.1 and 2.184.21

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-40846 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40846 is a high-severity vulnerability in HaloITSM ITSM, published on 8 May 2025. 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-2025-40846 in the wild and no public exploit code.

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

## Sources

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

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