dbcve.org
SiemApplication · Logpoint

CVE-2025-66359

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-28
Fix available
A fix is available. Upgrade to 7.7.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Logpoint before version 7.7.0 contains a cross-site scripting (XSS) vulnerability caused by insufficient input validation and lack of output escaping in multiple components. An attacker could inject malicious JavaScript code through unvalidated user inputs that are rendered without proper escaping, allowing script execution in the context of other users' sessions.

MitigationUpgrade Logpoint to version 7.7.0 or later to obtain the patched version. Prior to production deployment, validate the update in a staging environment to ensure compatibility with existing configurations and workflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SiemApplication
Affected:< 7.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Logpoint Siem version
    Access the Logpoint administration interface or check the installed package/version via the system console. Look for the version displayed in the product UI under 'About' or 'System Information', or query the installed Logpoint package using the system package manager if applicable.
    Affected if The installed version is below 7.7.0 (any version < 7.7.0 indicates the vulnerability is present)
  2. Locate user input components in the web interface
    Review the Logpoint web interface for components that accept user input, such as search fields, report builders, alert configurations, custom field inputs, and dashboard widgets. These are the potential injection points.
    Affected if User input fields exist in the interface and the version is < 7.7.0, meaning unvalidated inputs could be rendered without escaping
  3. Test for XSS in user input fields
    Using a controlled test environment, enter a benign XSS test payload (such as <script>alert('XSS')</script> or an img onerror tag) into visible user input fields within Logpoint. Observe whether the payload is executed or reflected back without encoding when the data is displayed in the UI.
    Affected if The test payload executes or renders as raw HTML/JavaScript instead of being escaped, confirming the vulnerability is exploitable
  4. Review custom scripts or integrations for output escaping
    If Logpoint includes custom scripts, connectors, or third-party integrations that display user-supplied data, inspect the code or configuration to verify whether output escaping functions are applied before rendering user input in web pages or dashboards.
    Affected if Custom components display user input without proper encoding and the Logpoint version is vulnerable

You are affected if your Logpoint Siem installation is version 7.6.x or earlier (below 7.7.0) and contains user input fields in the web interface that render data without escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.7.0 or later
Fixed in 7.7.0
Interim mitigation

Upgrade Logpoint to version 7.7.0 or later to obtain the patched version. Prior to production deployment, validate the update in a staging environment to ensure compatibility with existing configurations and workflows.

Recommended fix High confidence

7.7.0

  1. 1. Identify current Logpoint SIEM version by navigating to the Logpoint administration interface or checking system information.
  2. 2. Schedule a maintenance window and create a complete backup of the Logpoint configuration and database.
  3. 3. Download Logpoint version 7.7.0 or later from the official Logpoint download portal or support site (servicedesk.logpoint.com).
  4. 4. Follow Logpoint's standard upgrade procedure to install version 7.7.0, ensuring all pre-upgrade prerequisites are met.
  5. 5. After upgrade completion, verify the new version is 7.7.0 or later in the administration interface.
  6. 6. Test that the XSS vulnerability is remediated by confirming proper output encoding is functioning in affected components.
Caveat Review Logpoint 7.7.0 release notes for any breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Siem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66359 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data