Skip to main content
VulnerabilityPublished

CVE-2025-52637: HCL AION · SQL Injection

Affects HCL AIONSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
4.5Medium
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:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

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-52637 effectively, organizations should implement the following specific measures: 1) Conduct a thorough review of all offering configurations within HCL AION 2.0 to identify and correct any settings that could permit unintended SQL query execution. 2) Enforce strict access controls and least privilege principles to limit local user permissions, reducing the risk of exploitation by low-privilege users. 3) Implement robust input validation and query restriction mechanisms at the application level to prevent harmful SQL queries from being executed through configuration options. 4) Monitor and audit local user activities related to configuration changes and database query executions to detect suspicious behavior early. 5) Engage with HCL support or security advisories regularly to obtain patches or updates addressing this vulnerability once available. 6) Educate users with local access about the risks of interacting with vulnerable configurations and enforce policies to minimize unnecessary user interaction with sensitive system components. These targeted actions go beyond generic advice by focusing on configuration management, access control, and proactive monitoring tailored to the nature of 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…