dbcve.org
SiemApplication · Logpoint

CVE-2024-33859

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-07
Fix available
A fix is available. Upgrade to 7.4.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.4.0. HTML code sent through logs wasn't being escaped in the "Interesting Field" Web UI, leading to XSS.

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

Stored XSS vulnerability in Logpoint's web interface where HTML content in log entries is not properly escaped when displayed in the 'Interesting Field' feature, allowing authenticated attackers to inject malicious JavaScript through crafted log entries.

MitigationUpgrade to Logpoint 7.4.0 or later which implements proper HTML escaping for log content rendered in the web UI.

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.4.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 version
    Access the Logpoint web UI and navigate to the 'About' or 'System Info' section, typically found under Settings > System > About. Alternatively, check the login page footer or use the command line: logpoint --version or check /opt/logpoint/version if you have server access.
    Affected if The installed version is lower than 7.4.0
  2. Confirm web interface access
    Verify you can access the Logpoint web interface by logging in with valid credentials. The vulnerability requires an authenticated session to both inject and trigger the XSS.
    Affected if You have valid credentials and can log into the web interface
  3. Locate Interesting Field feature
    In the Logpoint web UI, navigate to the Search or Analytics section where the 'Interesting Field' feature displays extracted field values from log entries. This is typically found in the field exploration panel during log searches.
    Affected if The Interesting Field feature is visible and actively processing log data
  4. Inspect displayed log content for unsanitized HTML
    Examine log entries shown in the Interesting Field panel. Look for raw HTML tags (such as <script>, <img>, <svg>, or event handlers like onload/onerror) appearing literally in the displayed content rather than being escaped to HTML entities.
    Affected if Log entries display unescaped HTML tags or JavaScript code as rendered content rather than text

You are affected if your Logpoint installation is version 7.4.0 or lower and you use the web interface to view log entries in the Interesting Field feature where unescaped HTML/JavaScript may be rendering.

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.4.0 or later
Fixed in 7.4.0
Interim mitigation

Upgrade to Logpoint 7.4.0 or later which implements proper HTML escaping for log content rendered in the web UI.

Recommended fix Moderate confidence

7.4.0

  1. Verify current Logpoint SIEM version by checking the system information in the admin interface
  2. Download Logpoint version 7.4.0 or later from the official Logpoint support portal (servicedesk.logpoint.com)
  3. Review Logpoint upgrade documentation for your deployment type
  4. Create a full backup of the current configuration and database
  5. Execute the upgrade process according to Logpoint's standard upgrade procedure
  6. After upgrade, verify the 'Interesting Field' Web UI now properly escapes HTML characters in log entries
  7. Confirm the XSS vulnerability is resolved by testing with a benign HTML payload in log data
Caveat Review release notes for 7.4.0 to check for any configuration or feature changes that may require adjustment

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

Fix this in Siem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33859 — 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-2024-33859 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