CVE-2025-62318: HCL AION is affected by multiple security vulnerabilities.
HCL AION is affected by a vulnerability where JavaScript responses containing data could be referenced by external pages, potentially allowing sensitive information to be captured by an attacker-controlled page (JavaScript hijacking) under certain conditions.
Security readout for executives and security teams
Plain-English summary
HCL AION v2.1.0 may expose sensitive data when a user interacts with an attacker-controlled page under specific conditions. The attacker could potentially capture data from JavaScript responses. The reported severity is low because exploitation requires adjacent network access, high complexity, and user interaction, with no availability impact.
Executive priority
Treat this as a routine, time-bounded remediation item rather than an emergency. Confirm whether AION v2.1.0 is deployed, reduce unnecessary interface exposure, and follow HCL guidance. Escalate if sensitive data-bearing responses are externally reachable or business-critical information is involved.
Technical view
The issue is described as JavaScript hijacking: an external page may reference data-bearing JavaScript responses and capture sensitive information. CVSS 3.1 is 3.7 (AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N). The record associates CWE-352. Available evidence identifies HCL AION v2.1.0; other versions default to unaffected.
Likely exposure
Exposure is limited to organizations running HCL AION v2.1.0 where affected JavaScript responses are reachable under the required adjacent-network and user-interaction conditions. The supplied sources do not identify affected endpoints, configurations, or exposed data types.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or public weaponization. Exploitation is characterized as difficult, requiring adjacent network access, high complexity, and victim interaction without prior privileges.
Researcher notes
The description supports a JavaScript-hijacking condition, while the record maps CWE-352. The supplied evidence does not specify endpoints, response formats, prerequisites beyond the CVSS vector, confirmed data impact, or a named fixed version. Avoid assuming broader version exposure or active exploitation.
Mitigation direction
Identify and prioritize HCL AION v2.1.0 deployments.
Review HCL advisory KB0133084 for vendor-approved remediation or upgrade guidance.
Restrict access to AION interfaces while remediation is evaluated.
Apply vendor guidance through normal change control and confirm service functionality afterward.
Validation and detection
Inventory deployed HCL AION versions and confirm whether v2.1.0 is present.
Review accessible JavaScript responses for sensitive data and cross-origin exposure.
Confirm relevant interfaces are not reachable beyond their intended network boundaries.
After remediation, verify the vendor-recommended version or configuration is active.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.