{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52654 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52654 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52654 is a medium-severity cross-site scripting vulnerability in HCL MyXalytics, published on 3 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-52654 and fix it if it is affected.\n\nWhat it is: CVE-2025-52654 is a medium-severity cross-site scripting vulnerability in HCL MyXalytics, published on 3 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-52654 in the wild and no public exploit code.\n\nAffected product: HCL MyXalytics. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52654/ (Markdown: https://insights.sbomify.com/CVE-2025-52654/index.md)","id":"CVE-2025-52654","markdown":"https://insights.sbomify.com/CVE-2025-52654/index.md","name":"CVE-2025-52654","record":{"aliases":["GHSA-4phj-rv4r-gjvp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"HCL MyXalytics","requires_auth":"low_privilege","summary":"Attackers can inject malicious HTML into HCL MyXalytics via untrusted input, potentially leading to content manipulation or script execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HCL","cpe":[{"product":"dryice_myxalytics","vendor":"hcltech"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HCL MyXalytics is affected by an HTML Injection","id":"CVE-2025-52654","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"HCL MyXalytics is affected by a Cross-Domain Script Include vulnerability.","id":"CVE-2025-52655"},"packages":[],"prev":{"headline":"Cross Site Scripting vulnerability in the web application","id":"CVE-2025-52653"},"products":["HCL MyXalytics"],"published":"2025-10-03","related":[{"cvss_score":8.9,"headline":"HCL MyXalytics is affected by out-of-band resource load (HTTP) vulnerability","id":"CVE-2024-42168","kev_date_added":null,"published":"2025-01-11"},{"cvss_score":8.8,"headline":"Path Traversal Arbitrary File Read affects DRYiCE MyXalytics","id":"CVE-2023-45722","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":8.3,"headline":"Improper Access Control (Controller APIs) affects DRYiCE MyXalytics","id":"CVE-2023-50343","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":8.2,"headline":"Unauthenticated File Upload affects DRYiCE MyXalytics","id":"CVE-2023-45724","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":8.2,"headline":"A broken cryptographic algorithm impacts MyXalytics","id":"CVE-2023-50350","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":8.2,"headline":"Insecure key rotation affects MyXalytics","id":"CVE-2023-50351","kev_date_added":null,"published":"2024-01-03"},{"cvss_score":7.6,"headline":"Cross Site Scripting vulnerability in the web application","id":"CVE-2025-52653","kev_date_added":null,"published":"2025-10-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-10","vendors":["HCL Software"]},"summary":"Attackers can inject malicious HTML into HCL MyXalytics via untrusted input, potentially leading to content manipulation or script execution.","url":"https://insights.sbomify.com/CVE-2025-52654/"}