Private-message disclosure via missing report authorization
Published Jan 24, 2024 · Updated May 30, 2025
Improper authorization in Lemmy 0.17.0 through 0.19.0 allows remote authenticated users to read arbitrary private messages. The /api/v3/private_message/report handler accepts any message ID without verifying that the reporter is its recipient, then returns the message in private_message_report_view. A valid account and a guessed message ID are required; each successful request exposes message contents and creates a visible report.
Summary
What happened
Improper authorization in Lemmy 0.17.0 through 0.19.0 allows remote authenticated users to read arbitrary private messages. The /api/v3/private_message/report handler accepts any message ID without verifying that the reporter is its recipient, then returns the message in private_message_report_view. A valid account and a guessed message ID are required; each successful request exposes message contents and creates a visible report.
The record
- CVE
- CVE-2024-23649
- Published
- Jan 24, 2024
- Updated
- May 30, 2025
- Vendor
- LemmyNet
- Product
- Lemmy
- Classifications
- CWE-285, CWE-200, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2024CVE publishedPublication date reported by the CVE source.
- May 30, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.17.0, < 0.19.1
What conditions does exploitation require?
What is affected?
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
- Vendor advisory curl 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