CVE-2025-51869
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 · uneditedInsecure Direct Object Reference (IDOR) vulnerability in Liner thru 2025-06-03 allows attackers to gain sensitive information via crafted space_id, thread_id, and message_id parameters to the v1/space/{space_id}/thread/{thread_id}/message/{message_id} endpoint.
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 · moderate confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in the Liner application. The v1/space/{space_id}/thread/{thread_id}/message/{message_id} endpoint fails to properly validate user authorization before returning message data. Attackers can manipulate the space_id, thread_id, and message_id parameters to access sensitive messages they are not authorized to view.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Liner application is deployedReview your application inventory or running services to confirm the Liner product is in use. Check for processes, containers, or services named 'liner' or documentation referencing Liner.Affected if Liner application is present in your environment
-
Locate the affected API endpointReview API documentation, route definitions, or network traffic logs for requests to endpoints matching the pattern v1/space/{space_id}/thread/{thread_id}/message/{message_id}. Use grep or log search tools to find instances of this path structure.Affected if The v1/space/*/thread/*/message/* endpoint is exposed and accessible in your environment
-
Verify authentication is required for the endpointAttempt unauthenticated requests to the endpoint using a tool like curl or Burp Suite. Observe whether the API returns a 401 or 403 status code, or requires a valid authentication token.Affected if The endpoint can be accessed without valid authentication credentials
-
Test for IDOR by accessing messages from different spacesLog in as User A with access to one space. Using the affected endpoint, modify the space_id, thread_id, or message_id parameters to reference resources belonging to a different space or thread that User A should not have access to. Check if the API returns the message data.Affected if The API returns message data for resources the authenticated user does not own or have permission to access
-
Check authorization logs or middlewareReview application logs, API gateway logs, or authorization middleware code for the affected endpoint. Look for authorization validation logic that checks if the user owns or has access to the requested space_id, thread_id, and message_id before returning data.Affected if No explicit ownership or permission check is performed before returning message content
If the Liner application exposes the v1/space/{space_id}/thread/{thread_id}/message/{message_id} endpoint and allows authenticated users to retrieve messages from spaces, threads, or messages they do not own, the environment is affected by this IDOR vulnerability.
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.
From vendor dataImplement proper authorization checks at the endpoint to verify the authenticated user has permission to access the requested space, thread, and message before returning any data. Additionally, consider implementing indirect references (mapping internal IDs to random/temporary identifiers) to prevent enumeration.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-51869 — 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-51869 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