Skip to main content
CVE-2023-45696VulnerabilityPublished Updated

CVE-2023-45696: HCL Sametime · Vulnerability

Affects HCL SametimeSource CVE Database V5

0

Not known to be exploited · CVSS 4.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
HCL Software HCL SametimeAffected
  • =11.5
  • =11.6
  • =12.0
  • =12.0.1
Fixed in–

AI-suggested

European organizations should take specific steps beyond generic advice: 1) Audit and identify all deployments of HCL Sametime Legacy web chat clients within their environment. 2) Disable the autocomplete attribute on all sensitive input fields in the chat client configuration or through custom client-side scripting to prevent browsers from caching sensitive data. 3) Enforce endpoint security policies that restrict local access to authorized personnel only and implement disk encryption to protect stored browser data. 4) Educate users about the risks of storing sensitive information in browser autocomplete fields and encourage the use of secure password managers instead. 5) Monitor for updates or patches from HCL Software and plan timely upgrades to fixed versions once available. 6) Consider migrating from the Legacy web chat client to newer, more secure communication platforms if feasible. 7) Implement browser security configurations or group policies that limit or disable autocomplete features for enterprise-managed devices. These targeted mitigations will reduce the risk of sensitive data exposure through this vulnerability.

Description

Sametime is impacted by sensitive fields with autocomplete enabled in the Legacy web chat client. By default, this allows user entered data to be stored by the browser.

References

Community reviews

Loading reviews…