VulnerabilityPublished 10 Oct 2025

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

Affects HCL AIONSource CVE Database V5

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.2High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% 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:C/C:L/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: High
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 HCL AION	Affected =2.0	Fixed in–

AI-suggested

Monitor HCL’s official channels closely for the release of security patches addressing CVE-2025-52650 and apply them immediately upon availability.
In the interim, review and harden CSP configurations in affected applications to explicitly disallow 'unsafe-inline' scripts and avoid using nonce or hash bypasses that could be exploited.
Implement Web Application Firewalls (WAF) with rules to detect and block inline script injections and anomalous script execution patterns.
Employ Runtime Application Self-Protection (RASP) solutions that can detect and prevent unauthorized script execution at runtime.
Conduct security awareness training to reduce the risk of successful user interaction-based exploitation, emphasizing phishing and social engineering defenses.
Audit all web applications built on HCL AION 2.0 for CSP policy weaknesses and remediate any deviations from best practices.
Use Content Security Policy reporting features to monitor and analyze CSP violations to detect potential exploitation attempts.
Limit exposure of HCL AION-based applications to only necessary users and networks, employing network segmentation and access controls.
Review and update incident response plans to include scenarios involving CSP bypass and script injection attacks.

Description

Inline script execution allowed in CSP vulnerability has been identified in HCL AION v2.0

Impact

For European organizations, the vulnerability poses a significant risk to the integrity of web applications built on HCL AION 2.0. Successful exploitation can allow attackers to execute malicious scripts, potentially leading to unauthorized data modification, session hijacking, or further compromise of internal systems. Although confidentiality impact is rated low, the integrity impact is high, which can undermine trust in business processes and data accuracy. The requirement for user interaction means phishing or social engineering could be used to trigger the exploit. Given the widespread use of HCL enterprise products in sectors such as finance, manufacturing, and government across Europe, exploitation could disrupt critical business operations and lead to regulatory compliance issues under GDPR if personal data integrity is affected. The absence of known exploits currently provides a window for proactive defense, but the high CVSS score and CSP bypass nature indicate that the threat could escalate rapidly once weaponized. Availability is not impacted, so denial-of-service is unlikely, but the integrity compromise alone is sufficient to cause serious operational and reputational damage.

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 10 Oct 2025, 09:49 UTC

WeaknessesCWE-1032

Technical details

References

Community reviews

Related threats