dbcve.org
Unica Centralized Offer ManagementApplication · Hcltech

CVE-2025-31998

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-12
Fix available
A fix is available. Upgrade to 25.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
HCL Unica Centralized Offer Management is vulnerable to poor unhandled exceptions which exposes sensitive information. An attacker can exploit use this information to exploit known vulnerabilities launch targeted attacks, such as remote code execution or denial of service.

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 Centralized Offer Management contains poor unhandled exception handling that leaks sensitive information through error messages and stack traces. Attackers can exploit this information disclosure to gather system details, paths, versions, and configuration data needed to launch targeted remote code execution or denial of service attacks.

MitigationImplement comprehensive exception handling throughout the application with custom error pages that display user-friendly messages without exposing stack traces, file paths, or system configuration details. Ensure all exceptions are logged server-side only and never returned to clients.

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
Unica Centralized Offer ManagementApplication
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
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 version of HCL Unica Centralized Offer Management
    Locate the version information in the product installation directory, typically in a version file, about page, or product-specific metadata. Check the Unica application or system information panel if available.
    Affected if The installed version is below 25.1.0.1 (e.g., 25.0.x, 24.x, or earlier releases)
  2. Verify application server error handling configuration
    Inspect the application server configuration files (such as web.xml or equivalent) for error-page definitions. Look for entries that specify exception types and their corresponding error pages.
    Affected if Error pages are not configured or are configured to display verbose exception details to end users
  3. Check for stack trace exposure in HTTP responses
    Send a crafted or malformed request to the Unica web interface and observe the HTTP response. Alternatively, trigger known error conditions and inspect the returned error pages.
    Affected if The application returns full stack traces, Java exception messages, file paths, or system configuration details in error responses
  4. Review logging and diagnostic configuration
    Examine the application configuration files for settings controlling verbose error output, such as debug mode flags, exception logging levels, or development mode settings.
    Affected if Debug mode, verbose exception reporting, or detailed error output is enabled in production configuration

The environment is affected if HCL Unica Centralized Offer Management version is below 25.1.0.1 and the application exposes detailed exception information, stack traces, or system details in error responses to 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 comprehensive exception handling throughout the application with custom error pages that display user-friendly messages without exposing stack traces, file paths, or system configuration details. Ensure all exceptions are logged server-side only and never returned to clients.

Recommended fix High confidence

25.1.0.1

  1. Verify current Unica Centralized Offer Management version by accessing the HCL Unica dashboard or checking the installed product version
  2. Review HCL Unica Centralized Offer Management 25.1.0.1 release notes and upgrade documentation at support.hcl-software.com for any specific upgrade requirements
  3. Ensure a complete backup of the current Unica system including database, configuration files, and deployment artifacts
  4. Stop all Unica services and application servers before initiating the upgrade
  5. Upgrade Unica Centralized Offer Management to version 25.1.0.1 or later following the official HCL upgrade documentation
  6. Verify the upgrade was successful by checking the product version and ensuring all services start properly
  7. Test the application to confirm functionality and validate that error messages no longer expose sensitive system information

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

Fix this in Unica Centralized Offer Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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