Description

BookWyrm through 0.9.1 fails to validate user visibility permissions in the status edit endpoint, allowing authenticated attackers to read followers-only and direct-message reviews by enumerating sequential status IDs. Attackers can access the raw content of restricted statuses through the edit view, bypassing the privacy protections documented for these message types.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-09-05T10:16:40.963Z",
  "pubdate": "2026-09-05T10:16:40.963Z",
  "executiveSummary": "An improper authorization vulnerability exists in BookWyrm versions through 0.9.1, specifically within the status edit endpoint. The application fails to perform adequate server-side access control validation when a request is made to edit a status.\nThis flaw allows authenticated attackers to bypass intended visibility restrictions, including 'followers-only' and 'direct-message' privacy settings. By manipulating the status ID parameter in the edit endpoint, an attacker can access the raw content of restricted statuses that they are not authorized to view.\nThe vulnerability poses a significant risk to user privacy and data confidentiality within the BookWyrm ecosystem. An attacker with a standard authenticated account can perform enumeration attacks by cycling through sequential status IDs to scrape private content across the platform. This exposure of sensitive communications undermines the platform's privacy controls and could lead to the unauthorized disclosure of private interactions between users.\nExploitation requires an active authenticated session, but no elevated privileges are necessary. The simplicity of the attack vector, combined with the predictable nature of sequential ID generation, makes this a high-impact issue for platforms relying on BookWyrm for social content management.",
  "technicalDetails": "The vulnerability resides in the server-side logic responsible for handling status update requests. When a user requests to view the edit interface for a status, the application fails to verify whether the requesting user possesses the necessary permissions to view or interact with the specific status ID provided.\nThe root cause is a failure to enforce authorization checks during the status retrieval process within the edit controller. While the application UI might restrict the display of links based on visibility settings, the backend API endpoint does not validate the request context against the status's privacy configuration (e.g., 'followers-only' or 'direct').\nThe attack flow proceeds as follows: First, an authenticated attacker identifies a legitimate status edit URL path. Second, the attacker systematically iterates through integer-based sequential IDs—a common pattern for database primary keys—within the URL. Third, for every provided ID, the backend fetches the corresponding status object from the database and renders the raw content in the edit view template, regardless of the status's visibility metadata.\nBecause the application assumes that the edit request implies authorized access, it inadvertently exposes the raw content of restricted statuses in the response body. This effectively transforms the edit endpoint into an unauthenticated data disclosure mechanism for sensitive information.\nThe vulnerable component is the server-side status management module, which manages object serialization and access control policies for social statuses. Versions through 0.9.1 are confirmed to be impacted. Because the exploitation relies on standard HTTP requests directed at the application's API or controller endpoints, it is highly accessible to any authenticated user within the network, requiring no special administrative privileges or complex exploit payloads.\nPost-exploitation, an attacker can automate the harvesting of private user data by scripting requests to the vulnerable endpoint, leading to a bulk exfiltration of private communications, including direct messages. This bypasses the privacy architecture designed to limit content dissemination to specific social graphs, resulting in a complete compromise of the platform's intended privacy model."
}