Unauthorized private-status interactions via unchecked status IDs
Published Sep 5, 2026 · Updated Sep 10, 2026
Authorization bypass in BookWyrm 0 through 0.9.1 allows remote authenticated users to interact with private statuses by ID. The Favorite and Unfavorite views resolve status_id with models.Status.objects.get and create or remove Favorite records without a privacy filter or visibility check. A valid account and a known or enumerable private status ID are required; successful requests persist or remove interactions, broadcast ActivityPub activity, and reveal status existence through response differences.
Summary
What happened
Authorization bypass in BookWyrm 0 through 0.9.1 allows remote authenticated users to interact with private statuses by ID. The Favorite and Unfavorite views resolve status_id with models.Status.objects.get and create or remove Favorite records without a privacy filter or visibility check. A valid account and a known or enumerable private status ID are required; successful requests persist or remove interactions, broadcast ActivityPub activity, and reveal status existence through response differences.
The record
- CVE
- CVE-2026-86112
- Published
- Sep 5, 2026
- Updated
- Sep 10, 2026
- Vendor
- BookWyrm
- Product
- BookWyrm
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record 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 <=0.9.1
What conditions does exploitation require?
What is affected?
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
- Authenticated Favorite and Unfavorite IDOR 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