CVE-2025-62320: HCL Sametime · Cross-site Scripting
Affects HCL SametimeSource CVE Database V5
Not known to be exploited · CVSS 4.7 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCLSametime | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-62320, organizations should prioritize upgrading HCL Sametime to versions above 25.1.1 once patches become available from HCL. In the interim, administrators can implement strict input validation and output encoding on all user-supplied data rendered in web pages to prevent injection of malicious HTML or scripts. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. User awareness training to recognize suspicious links and avoid clicking untrusted URLs can reduce exploitation likelihood. Network-level protections such as web application firewalls (WAFs) configured with rules to detect and block XSS payloads may provide additional defense. Regular security assessments and code reviews focusing on input sanitization practices in custom integrations with Sametime are recommended. Monitoring logs for unusual user activity or error messages related to input handling can aid early detection of exploitation attempts.
Description
HTML Injection can be carried out in Product when a web application does not properly check or clean user input before showing it on a webpage. Because of this, an attacker may insert unwanted HTML code into the page. When the browser loads the page, it may automatically interact with external resources included in that HTML, which can cause unexpected requests from the user’s browser.