Conversation history disclosure via unchecked message identifiers
Published Jul 21, 2025 · Updated Jul 22, 2025
IDOR in the Liner chat API through 2025-06-03 allows remote authenticated users to read other users' conversation histories. The message endpoint disregards the supplied space and thread context and retrieves records by message_id without checking ownership or sharing status. An authenticated account can enumerate predictable, ascending nine-digit message identifiers; the demonstrated consequence is disclosure of stored chat history.
Summary
What happened
IDOR in the Liner chat API through 2025-06-03 allows remote authenticated users to read other users' conversation histories. The message endpoint disregards the supplied space and thread context and retrieves records by message_id without checking ownership or sharing status. An authenticated account can enumerate predictable, ascending nine-digit message identifiers; the demonstrated consequence is disclosure of stored chat history.
The record
- CVE
- CVE-2025-51869
- Published
- Jul 21, 2025
- Updated
- Jul 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-639, T1530
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 21, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Secsys-FDU conversation-history proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo