CVE-2025-52625VulnerabilityPublished 10 Oct 2025

CVE-2025-52625: HCL AION · CWE-525

Affects HCL AIONSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.7Low

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:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of integrity within 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 2026-10-26.

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 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

1. Immediately review and update web server and application configurations to ensure SSL pages are served with cache-control headers that prevent caching (e.g., Cache-Control: no-store, no-cache, must-revalidate; Pragma: no-cache). 2. Disable caching of SSL content at the browser level where possible, especially on shared or public devices. 3. Implement endpoint security controls to restrict unauthorized access to devices and browser caches, including disk encryption and user session management. 4. Educate users about the risks of using shared devices and the importance of logging out and clearing browser caches after sessions involving sensitive applications. 5. Monitor for any updates or patches from HCL addressing this vulnerability and apply them promptly once available. 6. Conduct regular security audits to verify that sensitive pages are not cached and that cache-control policies are enforced consistently across all environments. 7. Consider network-level controls that prevent caching of SSL traffic by proxies or intermediary devices. 8. In high-risk environments, consider deploying additional data loss prevention (DLP) solutions to detect and block unauthorized data exposure from cached content.

Description

A vulnerability Cacheable SSL Page Found vulnerability has been identified in HCL AION. Cached data may expose credentials, system identifiers, or internal file paths to attackers with access to the device or browser This issue affects AION: 2.0.

Impact

For European organizations, the primary impact is the potential exposure of sensitive information such as credentials and internal system details if an attacker gains access to cached SSL pages on user devices or browsers. This could facilitate further attacks such as unauthorized access or reconnaissance. The vulnerability does not directly allow remote exploitation or system compromise but increases risk in scenarios involving device theft, shared workstations, or insider threats. Confidentiality is impacted, but integrity and availability remain unaffected. The low CVSS score reflects the limited scope and complexity of exploitation. However, organizations in regulated sectors (e.g., finance, healthcare) may face compliance risks if sensitive data is exposed. The threat is more pronounced in environments with lax physical security or insufficient endpoint protection. Overall, the vulnerability represents a moderate operational risk that can be mitigated with proper configuration and access controls.

CWE-525Use of Web Browser Cache Containing Sensitive Information (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not use an appropriate caching policy that specifies the extent to which each web page and associated form fields should be cached.
Architecture and Design
Protect information stored in cache.
Implementation
Use a restrictive caching policy for forms and web pages that potentially contain sensitive information, such as "no-cache" in the Cache-Control header.
Architecture and Design
Do not store unnecessarily sensitive information in the cache.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.2.1 (opens in a new tab)
V8.1.1 (opens in a new tab)
V8.1.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

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, 10:46 UTC

WeaknessesCWE-525

Technical details

References

Community reviews

Related threats