CVE-2025-52616VulnerabilityPublished 12 Oct 2025Updated 15 Oct 2025

CVE-2025-52616: HCL Software Unica · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects HCL Software UnicaSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% 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:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCL Software Unica	Affected <=12.1.10	Fixed in–

AI-suggested

1. Monitor vendor communications closely for the release of official patches or updates addressing CVE-2025-52616 and apply them promptly. 2. Restrict network access to HCL Unica management interfaces using firewalls, VPNs, or IP whitelisting to limit exposure to unauthorized users. 3. Implement strict access controls and segmentation to isolate Unica servers from less trusted network zones. 4. Conduct regular security audits and vulnerability scans focusing on Unica deployments to detect anomalous information disclosures. 5. Enable detailed logging and monitor for unusual access patterns or reconnaissance activities targeting Unica systems. 6. Educate IT and security teams about the nature of information exposure vulnerabilities and the importance of minimizing system information leakage. 7. Consider deploying web application firewalls (WAFs) with custom rules to detect and block attempts to access sensitive system information. 8. Review and harden Unica configuration settings to minimize unnecessary information disclosure through error messages or debug outputs. 9. Develop incident response plans that include scenarios involving information exposure and subsequent exploitation attempts. 10. Engage with HCL support or security advisories to stay informed about emerging threats and mitigation strategies related to Unica.

Description

HCL Unica 12.1.10 can expose sensitive system information. An attacker could use this information to form an attack plan by leveraging known vulnerabilities in the application.

Impact

For European organizations, the exposure of sensitive system information in HCL Unica can increase the risk of targeted attacks by providing attackers with reconnaissance data necessary to exploit other vulnerabilities. While the vulnerability itself does not directly compromise data confidentiality or system availability, it lowers the barrier for attackers to plan and execute more damaging attacks, potentially leading to data breaches, unauthorized access, or service disruption. Organizations relying heavily on Unica for marketing and customer engagement may face operational impacts if attackers leverage this information to disrupt campaigns or exfiltrate data through chained exploits. The medium severity rating suggests moderate risk, but the lack of authentication and user interaction requirements increases the likelihood of exploitation attempts. European entities with regulatory obligations under GDPR must consider the indirect risk of data exposure resulting from chained attacks facilitated by this vulnerability. Additionally, the reputational damage and potential financial losses from successful attacks exploiting this information exposure could be significant.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124230 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Oct 2025, 05:24 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats