Skip to content
OpenAdvisories
Medium · 5.3 Scanner template CVE-2026-27454 EUVD-2026-13188

Discourse has check revision visibility on posts endpoint

Published Mar 19, 2026 · Updated Mar 20, 2026 · Assigned by GitHub_M

Description

Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, requesting /posts/:id.json?version=X bypassed authorization checks on post revisions. The display_post method called post.revert_to directly without verifying whether the revision was hidden or if the user had permission to view edit history. This meant hidden revisions (intentionally concealed by staff) could be read by any user by simply enumerating version numbers. Starting in versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, Discourse looks up the PostRevision and call guardian.ensure_can_see! before reverting, consistent with how the /posts/:id/revisions/:revision endpoint already authorizes access. No known workarounds are available.

Affected products

VendorProductAffectedFixed
discourse discourse >= 2026.1.0-latest, < 2026.1.2, >= 2026.2.0-latest, < 2026.2.1, = 2026.3.0-latest —

Automated scanner template

A ready-made Nuclei template detects this vulnerability automatically. Vulnerabilities with public scanner templates are typically probed across the internet soon after the template appears — exposed systems should be patched first.

Source: projectdiscovery/nuclei-templates (MIT) — updated daily. Only links are listed.

References