Cyber Resilience

CVE-2025-52660

Hcltech Aion 2.0.0

Published
19 January 2026
Modified
25 April 2026
CVSS Score v3.1 2.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0028 20th percentile
Risk Priority 25 floored blend · peak EPSS

Summary

CVE-2025-52660 is a low-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Hcltech Aion. Its CVSS base score is 2.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-52660 is an Unrestricted File Upload vulnerability affecting HCL AION. This flaw enables the upload of malicious files, which could potentially lead to unauthorized code execution or system compromise. The vulnerability is classified under CWE-644 and has a CVSS v3.1 base score of 2.7 (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N), indicating low severity primarily due to the high privileges required for exploitation.

Attackers with high-privilege access, such as authenticated administrators, can exploit this vulnerability over the network with low complexity and no user interaction required. Successful exploitation allows limited unauthorized access to confidential information, though the unchanged scope limits broader impacts on integrity or availability. While the description notes potential for code execution or system compromise, the scored impact remains low confidentiality disclosure.

The HCL Software support knowledge base article at https://support.hcl-software.com/kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995# provides details on mitigation, including any available patches or workarounds for HCL AION. Security practitioners should consult this advisory for specific remediation steps.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

HCL AION is affected by an Unrestricted File Upload vulnerability. This can allow malicious file uploads, potentially resulting in unauthorized code execution or system compromise.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52624Same product: Hcltech Aion
CVE-2025-52632Same product: Hcltech Aion
CVE-2025-52644Same product: Hcltech Aion
CVE-2025-52650Same product: Hcltech Aion
CVE-2025-52629Same product: Hcltech Aion
CVE-2025-52634Same product: Hcltech Aion
CVE-2025-55250Same product: Hcltech Aion
CVE-2026-4096Same vendor: Hcltech
CVE-2025-52641Same product: Hcltech Aion
CVE-2025-52659Same product: Hcltech Aion

Affected Assets

hcltech
aion
2.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.2.3

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly requires checking/neutralizing untrusted data such as HTTP headers before they reach browser components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing catches header-injection issues before release, covering most of the weakness.

prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.

prevents

Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.

prevents

Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.

References