Skip to main content
VulnerabilityPublished

CVE-2025-52653: HCL MyXalytics · XSS or 'Cross-site Scripting'

Affects HCL MyXalyticsSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 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

Affected software

ProductAffectedFixed in
HCL HCL MyXalyticsAffected
  • =6.6
Fixed in–

AI-suggested

European organizations should implement a multi-layered mitigation approach: 1) Immediate review and restriction of user privileges within HCL MyXalytics to minimize the number of users with the ability to trigger the vulnerability. 2) Employ web application firewalls (WAFs) with custom rules to detect and block malicious script injections targeting MyXalytics endpoints. 3) Conduct user awareness training focused on recognizing and avoiding phishing attempts that could lead to user interaction exploitation. 4) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing MyXalytics. 5) Monitor application logs and network traffic for unusual activity indicative of exploitation attempts. 6) Engage with HCL support channels to obtain patches or workarounds as soon as they become available and plan for prompt application of updates. 7) Consider isolating the MyXalytics environment or restricting access to trusted networks until the vulnerability is remediated. These steps go beyond generic advice by focusing on privilege management, proactive detection, and user behavior, tailored to the specifics of this XSS vulnerability.

Description

HCL MyXalytics product is affected by Cross Site Scripting vulnerability in the web application. This can allow the execution of unauthorized scripts, potentially resulting in unauthorized actions or access.

References

Community reviews

Loading reviews…