Skip to main content
VulnerabilityPublished

CVE-2025-62319: HCL Unica · SQL Injection

Affects HCL UnicaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
HCLUnicaAffected
  • =Version 25.1.1 and below
Fixed in–
Mavencom.hcl/unicapkg:maven/com.hcl/unicaOther threatsAffected
  • <=25.1.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-62319, organizations should immediately assess their use of HCL Unica and identify affected versions (25.1.1 and below). Although no official patches are currently available, organizations should implement the following specific measures: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns, especially Boolean-based injection attempts targeting Unica endpoints. 2) Conduct thorough input validation and sanitization on all user-supplied data, enforcing strict whitelisting of allowed characters and rejecting suspicious input before it reaches SQL queries. 3) Where possible, configure the application or database to use parameterized queries or prepared statements to prevent injection. 4) Monitor application logs and database query logs for anomalous patterns indicative of injection attempts, such as unexpected Boolean conditions or query delays. 5) Restrict database user privileges for the Unica application to the minimum necessary, limiting the potential damage from successful injection. 6) Isolate Unica servers within segmented network zones with strict access controls to reduce exposure. 7) Prepare incident response plans specific to SQL injection attacks, including data backup and recovery procedures. Organizations should also maintain close communication with HCL for updates on official patches or advisories.

Description

CVE-2025-62319 is a critical SQL injection vulnerability affecting HCL Unica versions 25.1.1 and below. It involves Boolean-based blind SQL injection, where attackers inject Boolean conditions into input fields to manipulate backend SQL queries without triggering visible errors. This flaw allows attackers to execute arbitrary SQL commands, potentially compromising database confidentiality, integrity, and availability. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. Although no known exploits are currently reported in the wild, the high CVSS score of 9.8 indicates severe risk. Organizations using affected versions of HCL Unica should prioritize patching or applying mitigations to prevent data breaches, unauthorized data manipulation, or service disruption. Countries with significant deployments of HCL Unica and strategic interest in marketing automation platforms are at higher risk.

References

Community reviews

Loading reviews…