CVE-2025-66360
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.7.0. An improperly configured access control policy exposes sensitive Logpoint internal service (Redis) information to li-admin users. This can lead to privilege escalation.
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 confidenceAn improperly configured access control policy in Logpoint before version 7.7.0 allows li-admin users to access sensitive internal Redis service information. This exposure of internal service data can be leveraged for privilege escalation beyond the intended li-admin role.
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.7.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine installed Logpoint versionAccess the Logpoint web interface and navigate to System Settings or About section to find the version number. Alternatively, check the installation logs or configuration files for version information.Affected if The installed version is below 7.7.0
-
Confirm Logpoint Siem product typeVerify the product is Logpoint Siem specifically, not another Logpoint product variant.Affected if The product is Logpoint Siem and version is below 7.7.0
-
Identify li-admin role usersReview the Logpoint user management interface to list accounts assigned the li-admin role.Affected if li-admin role accounts exist in a Logpoint Siem version below 7.7.0
The environment is affected if Logpoint Siem version is below 7.7.0 regardless of exploitation status.
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.7.0
Upgrade Logpoint to version 7.7.0 or later, which contains the properly configured access control policy that restricts Redis service information from li-admin users.
7.7.0
- Review the official Logpoint upgrade documentation at servicedesk.logpoint.com for complete upgrade procedures
- Ensure you have a complete backup of your current Logpoint configuration and data
- Plan your upgrade window considering your organization's maintenance policies
- Download Logpoint SIEM version 7.7.0 or later from the official Logpoint distribution channels
- Execute the upgrade following Logpoint's documented upgrade path for your current version
- After upgrade, verify that the access control policy changes have been applied correctly
- Test that li-admin users no longer have access to Redis internal service information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66360 — 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-2025-66360 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