What is the CVSS score of CVE-2025-66359?

CVE-2025-66359 has a CVSS 3.1 base score of 8.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Siem are affected by CVE-2025-66359?

Organizations using Logpoint face significant risk from CVE-2025-66359, a cross-site scripting vulnerability rated CVSS 8.5.

How to fix or mitigate CVE-2025-66359?

Within 7 days: Identify all affected systems running Logpoint and apply vendor patches promptly. Verify anti-CSRF tokens and content security policies are enforced.

Siem CVE-2025-66359

HIGH

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

2025-11-28 cve@mitre.org

XSS Siem

8.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:24 vuln.today

CVE Published

Nov 28, 2025 - 00:15 nvd

HIGH 8.5

DescriptionCVE.org

An issue was discovered in Logpoint before 7.7.0. Insufficient input validation and a lack of output escaping in multiple components leads to a cross-site scripting (XSS) vulnerability.

AnalysisAI

An issue was discovered in Logpoint before 7.7.0. Rated high severity (CVSS 8.5), this vulnerability is remotely exploitable. 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. An issue was discovered in Logpoint before 7.7.0. Insufficient input validation and a lack of output escaping in multiple components leads to a cross-site scripting (XSS) vulnerability. Affected products include: Logpoint Siem. Version information: before 7.7.0..

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.