Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Nov 8, 2026

CVE-2026-27454 Scanner

CVE-2026-27454 Scanner - Missing Authorization vulnerability in Discourse

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
9
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
5.3
CVSSmedium
Exploitable remotely over the internet · no authentication required.
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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
discourseby discourse
>= 2026.1.0-latest, < 2026.1.2
Updated Nov 6, 2026View on NVD →
Detail

Discourse is an open-source discussion platform used worldwide by various organizations and communities. It supports features like forums, discussion threads, and user engagement tools. Organizations utilize Discourse to enhance community engagement through interactive discussions and Q&A sessions. Its versatility makes it popular among educational institutions, businesses, and open-source communities. Administrators of Discourse configure its settings to manage user permissions, content visibility, and interaction policies. With a strong focus on user experience, Discourse offers various customization options to cater to different application needs.

The detected vulnerability relates to an improper authorization check in the Discourse application. By exploiting this vulnerability, unauthorized users could gain access to hidden post revisions. This issue arises due to missing checks for permissions when reverting posts to a specified version. Attackers can invoke endpoints that apply hidden post revisions without proper authorization checks. The vulnerability particularly affects posts with hidden revisions, allowing unauthorized recovery of concealed content. This problem exists in versions of Discourse up to 2026.2.0, calling for necessary updates to mitigate potential exploitation risks.

The vulnerability lies in the PostsController#display_post function, which oversees post version management. When an unauthorized request is made to revert posts to a version containing hidden revisions, the system fails to check user permissions. This lack of enforcement enables attackers to fetch hidden post content using queries with public version numbers. The technical failure happens when versions are reverted based on incoming GET requests without confirming appropriate view rights through guardian.ensure_can_see! evaluations. Patches in subsequent Discourse releases address this loophole by ensuring revisions and version requests are restricted to authorized users.

If exploited, the vulnerability would allow unauthorized individuals to access hidden post revisions that site moderators have opted to conceal. This could lead to unauthorized disclosure of content deemed sensitive or private by Discourse moderators. Additionally, it could undermine user trust in Discourse platforms, especially where information security and integrity are paramount. Exposure of modifications and hidden edits may pose reputational risks for the platform and permit unintended access to confident content. Users with ill intentions might leverage this fault to harm discussions' content control in affected Discourse installations.

REFERENCES

Solution Advice
  • Upgrade Discourse to version 2026.1.2, 2026.2.1, 2026.3.0-latest.1, or later to mitigate this vulnerability.
  • Enhance authorization checks within your web application to ensure only authenticated users can access content.
  • Regularly audit and update user permissions and roles to maintain adequate content access control.
  • Implement stringent logging and monitoring mechanisms to detect unauthorized access attempts promptly.
  • Consider employing additional access controls or security plugins available for Discourse to reinforce its security posture.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.