dbcve.org
UnicaApplication · Hcltech

CVE-2025-31996

HIGH · 7.5 CVSS v3.1 Published 2025-10-13
Fix available
A fix is available. Upgrade to 25.1.0.1 or later.
See remediation →
84/100
Remediation priority · High
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 Unica Platform is affected by unprotected files due to improper access controls.  These files may contain sensitive information such as private or system information that can be exploited by attackers to compromise the application, infrastructure, or users.

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 Unica Platform contains improperly protected files due to insufficient access controls. An unauthenticated or low-privilege attacker could access sensitive files on the system that expose private or system information, potentially leading to further compromise of the application or infrastructure.

MitigationImplement proper file access controls (file system permissions, authentication requirements, or path restrictions) on the affected files identified in the vulnerability assessment to ensure only authorized users can access sensitive file contents.

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.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Unica version
    Locate the Unica installation directory and check version files (typically in the 'tools' or 'config' subdirectory, or check the product.ini/readme files). Common locations include: HCL/Unica/platform or HCL/Unica/[module] directories.
    Affected if The installed version is any release prior to 25.1.0.1 (e.g., 24.x, earlier versions)
  2. Review file system permissions on Unica installation directory
    Use OS commands to inspect access controls: on Windows, right-click the Unica installation folder > Properties > Security tab; on Unix/Linux, run 'ls -la' or 'getfacl' on the Unica installation directory.
    Affected if Files or directories within the Unica installation allow read access to unauthenticated or low-privilege users (users other than the application service account)
  3. Verify sensitive configuration files are protected
    Check read permissions on configuration files (e.g., database connection files, XML configs, properties files) within the Unica installation. Attempt to read them using a low-privilege test account or anonymous access if applicable.
    Affected if Sensitive configuration, credential, or system information files are readable by unauthenticated or low-privilege users
  4. Test for unauthenticated file access
    If Unica has web endpoints, attempt to access common file paths (e.g., config files, logs) via HTTP/HTTPS without authentication to determine if files are exposed via the web application.
    Affected if The web application serves sensitive files to unauthenticated requests or returns file contents when accessed directly

You are affected if the installed HCL Unica version is below 25.1.0.1 AND sensitive files within the installation are readable by unauthenticated or low-privilege users.

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.0.1 or later
Fixed in 25.1.0.1
Interim mitigation

Implement proper file access controls (file system permissions, authentication requirements, or path restrictions) on the affected files identified in the vulnerability assessment to ensure only authorized users can access sensitive file contents.

Recommended fix Moderate confidence

25.1.0.1

  1. Obtain the HCL Unica Platform 25.1.0.1 installer from the official HCL support portal at support.hcl-software.com
  2. Review the HCL Unica Platform 25.1.0.1 release notes and upgrade documentation
  3. Create a complete backup of the current Unica installation including configuration files, database, and customizations
  4. Test the upgrade in a non-production environment before deploying to production
  5. Stop all Unica services and related components
  6. Run the 25.1.0.1 installer to upgrade the Platform component
  7. Verify the upgrade was successful by checking the version number in the Unica Platform interface
  8. Start Unica services and confirm all components are running properly

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

Fix this in Unica Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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