CVE-2025-52654: HCL MyXalytics · CWE-80
Affects HCL MyXalyticsSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% 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:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL Software HCL MyXalytics | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-52654, organizations should implement strict input validation and output encoding on all user-supplied data before rendering it in the application interface. Employing context-aware encoding (e.g., HTML entity encoding) prevents injection of executable HTML or scripts. Restricting user privileges to the minimum necessary reduces the likelihood of exploitation by low-privilege users. Monitoring and logging user inputs and application responses can help detect attempted injections. Additionally, educating users about phishing and suspicious content can reduce the effectiveness of injected malicious HTML. Regularly reviewing and updating security configurations and preparing for vendor patches once released is essential. Finally, isolating analytics platforms from direct internet exposure and enforcing strong authentication mechanisms will further reduce attack vectors.
Description
HCL MyXalytics v6.6 is affected by an HTML Injection. This issue occurs when untrusted input is included in the output without proper handling, potentially allowing unauthorized content injection and manipulation.