CVE-2026-86111

BookWyrm through 0.9.1 Insecure Direct Object Reference in EditStatus Exposes Followers-Only and Direct Statuses

Published Sep 5, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

BookWyrm 0.9.1 onward lacks visibility validation in its status edit endpoint. This allows any authenticated user to enumerate sequential status identifiers and access the raw content of followers‑only or direct‑message statuses by requesting the edit view. The resulting breach is the disclosure of private status content, exposing sensitive user interactions that were intended to be invisible to non-followers.

Affected Systems

BookWyrm, as published by bookwyrm‑social, is affected in releases up to and including 0.9.1. Users operating those versions run the risk of the described information‑disclosure flaw unless updated.

Risk and Exploitability

The CVSS score of 7.1 denotes a medium severity vulnerability, while the EPSS score is unavailable. The flaw is not listed in the CISA KEV catalog. Attackers need valid authentication and can perform ID enumeration by sequentially adjusting the status ID in the edit URL. Once the ID is within the authorized range, the endpoint serves payload without verifying the viewer's permission, making exploitation straightforward for an attacker with a normal user account.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update BookWyrm to a version that includes the IDOR fix (≥0.9.2).
  • If an upgrade is not immediately available, modify the status edit view to perform explicit visibility checks, granting access only to the status owner or public viewers.
  • Conduct a code review or automated audit to confirm that all status edit paths enforce visibility constraints, and monitor traffic for suspicious status ID enumeration attempts.

Generated by OpenCVE AI on September 5, 2026 at 11:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Bookwyrm-social
Bookwyrm-social bookwyrm
Vendors & Products Bookwyrm-social
Bookwyrm-social bookwyrm
Type Values Removed Values Added
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.
Title BookWyrm through 0.9.1 Insecure Direct Object Reference in EditStatus Exposes Followers-Only and Direct Statuses
First Time appeared Joinbookwyrm
Joinbookwyrm bookwyrm
Weaknesses CWE-639
CPEs cpe:2.3:a:joinbookwyrm:bookwyrm:*:*:*:*:*:*:*:*
Vendors & Products Joinbookwyrm
Joinbookwyrm bookwyrm
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:20 PM
Reserved
Sep 5, 2026, 1:59 AM
Status
Deferred
Published
Sep 5, 2026, 10:16 AM
Modified
Sep 8, 2026, 8:05 PM