VulnerabilityPublished 10 Oct 2025Updated 3 Feb 2026

CVE-2025-52624: HCL AION · CWE-1032

Affects HCL AIONSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCL AION	Affected =2.0	Fixed in–

AI-suggested

European organizations should immediately audit and review their Content-Security-Policy headers in HCL AION 2.0 deployments to ensure strict script allowlist enforcement. Specific steps include: 1) Implement a restrictive CSP that only allows scripts from trusted domains and disallows inline scripts unless absolutely necessary, using nonce or hash-based whitelisting. 2) Disable or limit the use of 'unsafe-inline' and 'unsafe-eval' directives in CSP. 3) Conduct thorough testing of CSP policies to verify that unauthorized scripts are blocked effectively. 4) Educate users about phishing risks to reduce the likelihood of user interaction exploitation. 5) Monitor web application logs for suspicious script execution or injection attempts. 6) Stay updated with HCL security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider deploying additional web application firewalls (WAF) with rules to detect and block XSS attempts. 8) Employ Content Security Policy reporting features to detect violations and refine policies accordingly. These targeted actions go beyond generic advice by focusing on CSP configuration hardening and proactive monitoring tailored to this vulnerability.

Description

A vulnerability Bypass of the script allowlist configuration in HCL AION. An incorrectly configured Content-Security-Policy header may allow unauthorized scripts to execute, increasing the risk of cross-site scripting and other injection-based attacks.This issue affects AION: 2.0.

Impact

For European organizations, this vulnerability poses a moderate risk, especially for those deploying HCL AION 2.0 in web-facing applications or internal portals. Exploitation could lead to unauthorized script execution, enabling attackers to perform cross-site scripting attacks that compromise user sessions, steal sensitive information, or manipulate application behavior. This can result in data breaches, loss of user trust, and potential regulatory non-compliance under GDPR if personal data is exposed. The impact is heightened for sectors with critical infrastructure or sensitive data, such as finance, healthcare, and government services. Since exploitation requires user interaction, phishing or social engineering campaigns could be used to trigger attacks. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability is widely known. The medium severity indicates that while the threat is not critical, it warrants timely attention to prevent escalation or chaining with other vulnerabilities.

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124444 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 08:29 UTC

WeaknessesCWE-1032

Technical details

References

Community reviews

Related threats