# CVE-2024-6201: HaloITSM - Emailing Template Injection

> Attackers can inject code into email templates to leak sensitive information from HaloITSM installations.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 6 Aug 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-53fg-j4pj-j8mf

## What is CVE-2024-6201?

CVE-2024-6201 is a medium-severity code injection vulnerability in HaloITSM, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HaloITSM versions up to 2.146.1 are affected by a Template Injection vulnerability within the engine used to generate emails. This can lead to the leakage of potentially sensitive information. HaloITSM versions past 2.146.1 (and patches starting from 2.143.61 ) fix the mentioned vulnerability.

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

It affects 1 product.


Products: Haloservicesolutions Haloitsm.

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

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

## Is CVE-2024-6201 being exploited?

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

## Other vulnerabilities in HaloITSM

- [CVE-2024-6202](https://insights.sbomify.com/CVE-2024-6202/): HaloITSM - SAML XML Signature Wrapping (XSW) (critical 9.8)
- [CVE-2024-6203](https://insights.sbomify.com/CVE-2024-6203/): HaloITSM - Password Reset Poisoning (high 8.3)
- [CVE-2024-6200](https://insights.sbomify.com/CVE-2024-6200/): HaloITSM - Stored Cross-Site Scripting in Tickets (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6201 is a medium-severity code injection vulnerability in HaloITSM, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6201 in the wild and no public exploit code.

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

## Sources

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

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