What is the CVSS score of CVE-2022-42450?

CVE-2022-42450 has a CVSS 3.1 base score of 4.6 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.1%.

Which versions of Domino Leap are affected by CVE-2022-42450?

Organizations using Improper sanitization of SVG files in HCL Domino Volt should be aware of moderate risk from CVE-2022-42450, a cross-site scripting vulnerability rated CVSS 4.6.

How to fix or mitigate CVE-2022-42450?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

Domino Leap CVE-2022-42450

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2025-04-30 psirt@hcl.com

XSS Domino Leap

4.6

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.6 MEDIUM

AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:39 vuln.today

CVE Published

Apr 30, 2025 - 22:15 nvd

MEDIUM 4.6

DescriptionCVE.org

Improper sanitization of SVG files in HCL Domino Volt allows client-side script injection in deployed applications.

AnalysisAI

Improper sanitization of SVG files in HCL Domino Volt allows client-side script injection in deployed applications. Rated medium severity (CVSS 4.6), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Improper sanitization of SVG files in HCL Domino Volt allows client-side script injection in deployed applications. Affected products include: Hcltech Domino Leap.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.