CVE-2024-56087
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 · uneditedAn issue was discovered in Logpoint before 7.5.0. Authenticated users can inject payloads while querying Search Template Dashboard. These are executed, leading to Server-Side Template Injection.
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 confidenceAuthenticated Logpoint users can inject malicious template payloads through the Search Template Dashboard query interface. These payloads are rendered server-side, enabling Server-Side Template Injection (SSTI) that can lead to arbitrary code execution on the affected system.
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< 7.5.0CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Logpoint Siem versionLocate the installed Logpoint version through the web interface (typically in System > About or Help menu) or via command-line tools used for Logpoint administrationAffected if The installed version is lower than 7.5.0
-
Confirm Search Template Dashboard accessNavigate to or enumerate the Search Template Dashboard feature in the Logpoint web interface and verify if authenticated users can access the query interfaceAffected if The Search Template Dashboard query interface is available to the authenticated user account being assessed
-
Check for existing malicious templatesReview saved Search Templates for unexpected syntax, Jinja2 template markers, or code patterns that may indicate exploitation attempts in the template storageAffected if Templates contain suspicious template injection syntax or unexpected code patterns
-
Audit administrative query accessReview user role permissions and access logs for the Search Template Dashboard and query interfaces to determine which authenticated users can submit templatesAffected if Authenticated users with query access exist in the environment and the version is below 7.5.0
Environment is affected if Logpoint Siem version is below 7.5.0 and authenticated users have access to the Search Template Dashboard query interface.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.5.0
Upgrade Logpoint to version 7.5.0 or later to patch the SSTI vulnerability. Restrict and monitor administrative query interfaces until the upgrade is applied.
7.5.0
- Obtain Logpoint SIEM version 7.5.0 from the official Logpoint download repository or vendor support channel
- Follow the standard Logpoint upgrade procedure to apply version 7.5.0
- Verify the upgrade was successful and the Search Template Dashboard functionality is restored
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56087 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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