Skip to main content
CVE-2025-52623VulnerabilityPublished

CVE-2025-52623: HCL AION · CWE-522

Affects HCL AIONSource CVE Database V5

0

Not known to be exploited · CVSS 3.7 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
HCLAIONAffected
  • =2.0
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations using HCL AION 2.0 should: 1) Immediately review and update the application’s HTML forms to explicitly set the autocomplete attribute to 'off' for all password input fields, preventing browsers from storing credentials. 2) Conduct security audits of web applications to identify and remediate similar autocomplete misconfigurations. 3) Educate users about the risks of saving passwords in browsers, especially on shared or unmanaged devices. 4) Implement endpoint security controls to detect and prevent unauthorized access to stored credentials, including the use of password managers that securely handle credentials outside the browser’s autocomplete mechanism. 5) Monitor for suspicious activities that may indicate credential compromise, such as unusual login patterns. 6) Engage with HCL for any forthcoming patches or updates addressing this issue and apply them promptly once available. 7) Enforce multi-factor authentication (MFA) to reduce the impact of potential credential disclosure. These steps go beyond generic advice by focusing on both application-level fixes and user/device-level controls.

Description

HCL AION is affected by an Autocomplete HTML Attribute Not Disabled for Password Field vulnerability. This can allow autocomplete on password fields may lead to unintended storage or disclosure of sensitive credentials, potentially increasing the risk of unauthorized access. This issue affects AION: 2.0.

References

Community reviews

Loading reviews…