# CVE-2025-52651: HCL MyXalytics is affected by multiple security vulnerabilities.

> HCL MyXalytics suffers from improper input validation, allowing malicious data to cause unintended system behavior or security issues.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-frcx-2mrg-6xg4

## What is CVE-2025-52651?

CVE-2025-52651 is a low-severity vulnerability in HCL Software MyXalytics, published on 7 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

HCL MyXalytics was affected by Improper Input validation Vulnerability. It allow malicious or unexpected data to cause unintended system behaviour or security issues.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-52651?


## How do I fix CVE-2025-52651?

No fix has been published for CVE-2025-52651 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52651 being exploited?

There is no known exploitation of CVE-2025-52651 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52651 and fix it if it is affected.

What it is: CVE-2025-52651 is a low-severity vulnerability in HCL Software MyXalytics, published on 7 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-52651 in the wild and no public exploit code.

Affected product: HCL Software MyXalytics. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52651/ (Markdown: https://insights.sbomify.com/CVE-2025-52651/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52651
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52651
- OSV: https://osv.dev/vulnerability/CVE-2025-52651

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52651/
Summaries are generated and may contain mistakes; the official description above is the record.