Discourse
CVE-2026-33423
LOW
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2021 - Broken Access Control
ASVS 5.0
V4 - Access Control Authorization enforcement, RBAC validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The risk assessment is complicated by the absence of CVSS and EPSS scores, but several contextual factors indicate moderate-to-high priority. The vulnerability requires authentication and staff-level privileges to exploit, which reduces the attack surface compared to unauthenticated exploits. However, the impact is significant: any staff member (not just administrators) can modify group notification preferences for any user, potentially leading to information disclosure, denial of service (by silencing notifications), or social engineering through forced notification changes. The fact that patches are available for multiple version lines (2026.1.2, 2026.2.1, 2026.3.0-latest.1) suggests this was treated seriously by the vendor. The vulnerability falls into the SSVC category of 'Authenticated Privilege Escalation' with moderate technical impact (user preference manipulation rather than data exfiltration or system compromise). Organizations should prioritize patching to prevent lateral privilege abuse by staff members, though the risk is lower than network-accessible unauthenticated flaws. |
| Exploit ScenarioDerived | A moderator or staff member with legitimate group management permissions logs into the Discourse instance and navigates to the group notification settings interface. Instead of only modifying notification levels for their intended group or purpose, they exploit the missing authorization checks to modify notification levels for arbitrary users across other groups, potentially silencing critical notifications that those users should receive or escalating notification frequency to cause harassment. Since the exploit requires valid staff credentials and operates through the normal group management interface, detection may be difficult without detailed audit logging; an attacker could perform this with standard HTTP requests to the group notification API endpoint without needing a public proof-of-concept tool. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 20, 2026
A privilege escalation vulnerability in Discourse allows staff members to arbitrarily modify group notification levels for any user without proper authorization checks. This affects Discourse versions prior to 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, enabling authenticated staff users to alter notification settings for other users in ways they should not be permitted to do. While no CVSS score or EPSS data is available and no known public exploits have been confirmed, the vulnerability is classified under CWE-862 (Missing Authorization) and has been assigned a GitHub Security Advisory (GHSA-qggq-wr6h-vhrg) with patches available.
RemediationAI
Organizations running Discourse should immediately upgrade to version 2026.3.0-latest.1, 2026.2.1, or 2026.1.2 or later depending on their current version line, as patches are available for all affected versions and no workarounds are documented. Administrators should consult the GitHub Security Advisory at https://github.com/discourse/discourse/security/advisories/GHSA-qggq-wr6h-vhrg for version-specific upgrade instructions and validation steps. Until patching is completed, restrict staff member access to group management features by auditing role assignments and enforcing principle of least privilege for administrative accounts. Additionally, review recent group notification level changes in audit logs to identify any unauthorized modifications that may have occurred while the system was vulnerable.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Discourse is an open-source discussion and community platform built on Ruby on Rails. The vulnerability exists in the group notification level management subsystem, which should enforce role-based access control (RBAC) to ensure only authorized administrators can modify notification preferences for users and groups. The root cause is classified as CWE-862 (Missing Authorization), indicating that the application fails to perform proper authorization checks before allowing staff members to execute group notification modifications. This represents a common authorization bypass flaw where privilege checks are either missing or improperly implemented in the endpoint responsible for updating group notification levels. The affected product is identified via CPE as cpe:2.3:a:discourse:discourse, spanning multiple version lines (2026.1.x, 2026.2.x, and 2026.3.0-latest versions).
Know when Discourse gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
DescriptionGitHub Advisory
Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, staff can modify any user's group notification level. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.
Executive ViewAI
CVE-2026-33423 is a low-severity vulnerability in Discourse involving missing authorization (CVSS 1.3). The limited severity suggests constrained impact, typically requiring specific conditions or local access for exploitation. Apply vendor updates when available as part of routine maintenance.
Apply vendor patch during routine maintenance. Standard security controls provide adequate interim protection.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)GitHub Advisory
Discourse versions prior to 3.5.0.beta6 contain a reflected cross-site scripting (XSS) vulnerability in social login fun
discourse-bbcode is the official BBCode plugin for Discourse. Rated critical severity (CVSS 9.8), this vulnerability is
Unauthorized information disclosure in Discourse discussion platform versions prior to 2026.3.0-latest.1, 2026.2.1, and
Discourse is an open source platform for community discussion. Rated high severity (CVSS 8.2), this vulnerability is rem
Discourse versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 contain an insecure direct object reference (IDOR) in the
In Discourse 2.7.0 through beta1, a rate-limit bypass leads to a bypass of the 2FA requirement for certain forms. Rated
Unauthenticated attackers can submit forged webhook payloads to multiple email provider integrations in Discourse versio
Discourse is an open-source discussion platform. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploi
Discourse is an open source platform for community discussion. Rated medium severity (CVSS 5.9), this vulnerability is r
Discourse versions prior to 3.4.4 (stable), 3.5.0.beta5 (beta), and 3.5.0.beta6-dev (tests-passed) contain a critical vu
Discourse is an open source platform for community discussion. Rated critical severity (CVSS 9.8), this vulnerability is
Discourse Patreon enables syncronization between Discourse Groups and Patreon rewards. Rated critical severity (CVSS 9.8
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB