Restricted-status disclosure via unchecked EditStatus object lookup
Published Sep 5, 2026 · Updated Sep 8, 2026
Authorization bypass in BookWyrm 0 through 0.9.1 allows remote authenticated users to read restricted statuses via the edit endpoint. EditStatus fetches a caller-supplied sequential status ID with get_object_or_404 but omits raise_visible_to_user and privacy_filter, then renders draft.raw_content in a textarea. Any valid account can enumerate IDs and read followers-only or direct reviews, comments, and quotations; the demonstrated path does not permit unauthorized edits.
Summary
What happened
Authorization bypass in BookWyrm 0 through 0.9.1 allows remote authenticated users to read restricted statuses via the edit endpoint. EditStatus fetches a caller-supplied sequential status ID with get_object_or_404 but omits raise_visible_to_user and privacy_filter, then renders draft.raw_content in a textarea. Any valid account can enumerate IDs and read followers-only or direct reviews, comments, and quotations; the demonstrated path does not permit unauthorized edits.
The record
- CVE
- CVE-2026-86111
- Published
- Sep 5, 2026
- Updated
- Sep 8, 2026
- Vendor
- BookWyrm
- Product
- BookWyrm
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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 EditStatus 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