Skip to main content
VulnerabilityPublished

CVE-2025-52646: HCL AION · SQL Injection

Affects HCL AIONSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.2 Low.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
HCLAIONAffected
  • =2.0
Fixed in–

AI-suggested

To mitigate CVE-2025-52646, organizations should: 1) Conduct a thorough audit of all offering configurations in HCL AION 2.0 to identify and restrict any that allow execution of arbitrary or potentially harmful SQL queries. 2) Implement strict input validation and parameterization for all database queries within the application to prevent injection or unintended query execution. 3) Limit user privileges to the minimum necessary, especially restricting local access to trusted users only. 4) Monitor logs for unusual database query patterns or errors that could indicate attempted exploitation. 5) Engage with HCL support channels to obtain any forthcoming patches or official guidance. 6) Educate users about the risks of interacting with untrusted content or configurations that could trigger this vulnerability. 7) Consider network segmentation and endpoint protection to reduce the risk of local exploitation. These steps go beyond generic advice by focusing on configuration management, privilege restriction, and proactive monitoring specific to this vulnerability.

Description

HCL AION is affected by a vulnerability where certain offering configurations may permit execution of potentially harmful SQL queries. Improper validation or restrictions on query execution could expose the system to unintended database interactions or limited information exposure under specific conditions.

References

Community reviews

Loading reviews…