Skip to main content
VulnerabilityPublished Updated

CVE-2025-44593: Halo · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium · fixed in 2.20.13 : update affected systems when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.20.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate upgrade to Halo version 2.20.13 or later to apply the official patch that fixes the file type detection bypass.
  2. Implement strict server-side validation of uploaded files, including MIME type verification and content inspection, to prevent malicious files from being accepted.
  3. Employ Content Security Policy (CSP) headers to limit the impact of any potential XSS by restricting script execution sources.
  4. Sanitize and encode all user-generated content before rendering it in browsers to mitigate stored XSS risks.
  5. Monitor file upload logs and web application logs for unusual activity or attempts to upload disallowed file types.
  6. Conduct regular security assessments and penetration testing focused on file upload functionalities.
  7. Educate users about the risks of interacting with suspicious content and encourage reporting of anomalies.
  8. If possible, isolate the Halo application environment to limit lateral movement in case of compromise.

Description

Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .html files. Specifically, .html files can trigger stored XSS vulnerabilities. This vulnerability is fixed in 2.20.13

References

Community reviews

Loading reviews…