dbcve.org
UnicaApplication · Hcltech

CVE-2025-62319

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 25.1.1.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Boolean-Based SQL Injection is a type of blind SQL injection where an attacker manipulates SQL queries by injecting Boolean conditions (TRUE or FALSE) into application input fields. Instead of returning database errors or visible data, the application responds differently depending on whether the injected condition evaluates to true or false. This allows an attacker to inject arbitrary SQL into backend configuration queries executed within the application.

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

Boolean-based blind SQL injection in backend configuration queries allows attackers to inject arbitrary SQL by manipulating TRUE/FALSE conditions in application input fields. The application exhibits different behavior based on whether injected conditions evaluate to true or false, enabling data exfiltration and potential database compromise.

MitigationImplement parameterized queries/prepared statements for all user-supplied inputs in configuration queries, perform comprehensive input validation, and audit all database interaction points.

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
UnicaApplication
Affected:< 25.1.1.0.1
Unica Audience CentralApplication
Affected:< 25.1.1.0.1

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
High
Integrity
High
Availability
High

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

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 Hcltech Unica version
    Access the Unica administrative interface or check the product version file/documentation. Common methods include viewing the 'About' section in the admin panel, checking the installer logs, or running: [version_check_command] depending on your deployment method.
    Affected if The installed version is below 25.1.1.0.1 (e.g., 25.0.x, 24.x, or earlier)
  2. Identify installed Hcltech Unica Audience Central version
    Access the Audience Central administrative interface or check the product version file. Navigate to the system information or about page in the Audience Central admin panel.
    Affected if The installed version is below 25.1.1.0.1 (e.g., 25.0.x, 24.x, or earlier)
  3. Locate backend configuration query endpoints
    Review application URL paths and API endpoints related to configuration, settings, or system parameters. Common patterns include paths containing 'config', 'settings', 'system', 'admin', or 'configure'. Use web application scanning or manual review of available routes.
    Affected if Configuration-related endpoints are exposed and accessible without additional authentication barriers beyond standard login
  4. Identify user input fields in configuration queries
    Test all input fields in configuration-related pages (forms, query parameters, search fields) by submitting TRUE and FALSE conditional payloads such as '1=1' vs '1=2' or 'AND 1=1' vs 'AND 1=2'. Compare HTTP response times, error messages, or output differences.
    Affected if The application exhibits measurably different behavior (response content, error messages, timing, or HTTP status) between TRUE and FALSE conditions in user-supplied input within configuration contexts

You are affected if you are running any version of Hcltech Unica or Hcltech Unica Audience Central prior to 25.1.1.0.1 AND your configuration query endpoints accept user input that produces different responses when injecting TRUE versus FALSE SQL conditions.

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 25.1.1.0.1 or later
Fixed in 25.1.1.0.1
Interim mitigation

Implement parameterized queries/prepared statements for all user-supplied inputs in configuration queries, perform comprehensive input validation, and audit all database interaction points.

Recommended fix High confidence

25.1.1.0.1

  1. 1. Create a complete backup of the current Unica and Unica Audience Central installation, including database and configuration files.
  2. 2. Navigate to the HCL Software support portal (support.hcl-software.com) and locate the download for Unica version 25.1.1.0.1.
  3. 3. Download the appropriate patch or installer for your specific Unica product and platform.
  4. 4. Review the HCL Unica installation/upgrade documentation for version 25.1.1.0.1 before proceeding.
  5. 5. Stop all Unica services and application servers to prevent active connections during the upgrade.
  6. 6. Execute the upgrade or patch installation following the official HCL upgrade procedures.
  7. 7. After installation, verify that all services start correctly.
  8. 8. Test the application to confirm functionality, particularly any features that execute backend configuration queries.
Caveat Review HCL release notes for 25.1.1.0.1 to check for any configuration or feature changes that may require adjustments

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

Fix this in Unica Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62319 — 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-62319 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