Categories
CVE-2025-52658 low CVSS 3.5

Vulnerability in HCL MyXalytics (CVE-2025-52658)

Summary

Vulnerability in HCL MyXalytics (CVE-2025-52658). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

HCL MyXalytics is affected by the use of vulnerable/outdated versions which can expose the application to known security risks that could be exploited.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-52658 has been found in HCL MyXalytics.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "HCL MyXalytics CVE-2025-52658" on the vendor's site.

CVE-2025-52658 (HCL MyXalytics) — CWE-1104 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-1104) exists in HCL MyXalytics.

📍 Affected scope

Check the vendor advisory for the affected versions of HCL MyXalytics.

🔥 Severity

Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで HCL MyXalytics を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details