CVE-2026-33251
Authorization Bypass in Discourse Allows Unauthorized Solution Acceptance
Publication date: 2026-03-20
Last updated on: 2026-03-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| discourse | discourse | From 2026.1.0 (inc) to 2026.1.2 (exc) |
| discourse | discourse | From 2026.2.0 (inc) to 2026.2.1 (exc) |
| discourse | discourse | 2026.3.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Discourse, an open-source discussion platform, in versions prior to 2026.3.0-latest.1, 2026.2.1, and 2026.1.2. It is an authorization bypass issue related to hidden Solved topics, which may allow unauthorized users to accept or unaccept solutions.
How can this vulnerability impact me? :
The impact of this vulnerability is that unauthorized users could manipulate the status of solutions in hidden Solved topics by accepting or unaccepting them. This could lead to misinformation or confusion about which solutions are valid or accepted within the discussion platform.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should ensure that only trusted users are part of the Site Setting for accept_all_solutions_allowed_groups.
Additionally, apply the patch by upgrading Discourse to one of the fixed versions: 2026.3.0-latest.1, 2026.2.1, or 2026.1.2.