CVE-2024-6200: HaloITSM versions up to 2.146.1 are affected by a Stored Cross-Site Scripting (XSS) vulnerability

Routine

HIGH 8.0UPGRADE

CVE-2024-6200 is a high-severity flaw (CVSS 8.0) affecting haloitsm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

HaloITSM versions up to 2.146.1 are affected by a Stored Cross-Site Scripting (XSS) vulnerability. The injected JavaScript code can execute arbitrary action on behalf of the user accessing a ticket. HaloITSM versions past 2.146.1 (and patches starting from 2.143.61 ) fix the mentioned vulnerability.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.0 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-08-06
Last modified	2026-06-17

Publisher (CNA): Switzerland Government Common Vulnerability Program · Vendor: haloservicesolutions

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-06 06:15 UTCPublished CVE record published
2026-06-17 08:17 UTCUpdated Record last modified

haloservicesolutions haloitsm UPGRADE

Affected: < 2.143.61 · >= 2.144 and < 2.146.1

Fixed in: 2.143.61, 2.146.1

Safe to downgrade to: a release before 2.144

1. Check installed version

apt-cache policy haloitsm || rpm -q haloitsm || haloitsm --version

2. UPGRADE to 2.143.61 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade haloitsm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade haloitsm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.144 (Debian / Ubuntu)

apt-cache madison haloitsm sudo apt install haloitsm=<VERSION_BEFORE_2.144> sudo apt-mark hold haloitsm

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list haloitsm sudo dnf downgrade haloitsm-<VERSION_BEFORE_2.144> sudo dnf versionlock add haloitsm

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-6200?

haloitsm: upgrade to 2.143.61, 2.146.1. Exact commands for each OS are on this page.

Is CVE-2024-6200 being exploited?

CVE-2024-6200 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-6200 affect?

CVE-2024-6200 affects haloitsm. Severity is high (CVSS 8.0). HaloITSM versions up to 2.146.1 are affected by a Stored Cross-Site Scripting (XSS) vulnerability. The injected JavaScript code can execute arbitrary action on behalf of the user accessing a ticket. HaloITSM versions past 2.146.1 (and patch

How urgent is CVE-2024-6200?

Priority 35/100. High severity

Related CVEs

CVE-2024-6203 HIGH 8.3 UPGRADE HaloITSM versions up to 2.146.1 are affected by a Password Reset Poisoning vulnerability
CVE-2024-6202 CRITICAL 9.8 UPGRADE HaloITSM versions up to 2.146.1 are affected by a SAML XML Signature Wrapping (XSW) vulnerability
CVE-2024-6201 MEDIUM 5.3 UPGRADE HaloITSM versions up to 2.146.1 are affected by a Template Injection vulnerability within the engine used to g

References

← Back to latest CVEs