dbcve.org
AionApplication · Hcltech

CVE-2025-52646

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 2.1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HCL AION contains a vulnerability where certain offering configurations permit execution of potentially harmful SQL queries due to improper validation or restrictions on query execution, potentially allowing unintended database interactions or limited information exposure.

MitigationImplement proper input validation and parameterized queries, restrict query execution permissions, and review offering configurations to ensure SQL query parameters are properly validated and constrained.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AionApplication
Affected:>= 2.0.0, < 2.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HCL AION version
    Check the AION installation directory for version files, or run the product's version command (typically found in bin/ directory or via product documentation). Common locations include version.txt in the install root or using 'aion -version' if available.
    Affected if The installed version is 2.0.0 through 2.1.1 (any version >= 2.0.0 but < 2.1.2)
  2. Review enabled offering configurations
    Examine the AION configuration files for enabled offerings. Look in config/ or etc/ directories for files like offerings.conf, aion-config.xml, or similar configuration files that define which offerings are active.
    Affected if Any offering configuration is enabled that permits direct SQL query execution or includes database interaction features
  3. Inspect SQL query execution settings
    Search configuration files for parameters related to query execution, SQL validation, or database interaction. Look for settings like 'allowSQL', 'queryExecution', 'enableRawQuery', or similar flags that control whether arbitrary SQL can be executed.
    Affected if SQL query execution is permitted or not properly restricted in the configuration
  4. Check offering-specific query permissions
    Review offering-specific configuration files (often in conf/offerings/ or similar paths) to identify which offerings have database query permissions enabled, particularly any that allow custom or direct SQL queries.
    Affected if Any offering has permissions that allow unrestricted or improperly validated SQL query execution

A user is affected if HCL AION version is between 2.0.0 and 2.1.1 inclusive AND an offering configuration is enabled that permits SQL query execution without proper validation or restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.2 or later
Fixed in 2.1.2
Interim mitigation

Implement proper input validation and parameterized queries, restrict query execution permissions, and review offering configurations to ensure SQL query parameters are properly validated and constrained.

Recommended fix Moderate confidence

2.1.2

  1. 1. Back up your current HCL AION database and configuration files
  2. 2. Download HCL AION version 2.1.2 from the official HCL support portal (support.hcl-software.com)
  3. 3. Review the official HCL AION upgrade documentation for version 2.1.2
  4. 4. Stop the HCL AION services before applying the upgrade
  5. 5. Apply the upgrade to version 2.1.2 following the documented procedures
  6. 6. Start the HCL AION services and verify the application is running
  7. 7. Test that SQL query functionality is working as expected after the upgrade
  8. 8. Verify the vulnerability is resolved by reviewing system logs for any SQL injection attempts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52646 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data