Skip to main content

Discourse EUVDEUVD-2026-13526

| CVE-2026-32114 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-03-20 security-advisories@github.com
4.3
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Impact

The CVSS 4.0 score of 5.3 with a vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N reflects a network-accessible vulnerability with low attack complexity and low privilege requirements, but low confidentiality impact and no integrity or availability impact. The risk assessment is moderately elevated by several factors: the vulnerability requires only authentication (not a special role), the attack vector is network-based with no user interaction required, and patches are readily available from the vendor. However, the actual real-world risk remains moderate rather than critical because the disclosed information (credit allocations and usage statistics) does not directly enable lateral privilege escalation, data destruction, or system compromise. The vulnerability is most concerning in multi-tenant Discourse deployments where different organizations use the same instance, as one tenant could surveil another's AI resource consumption. For single-tenant or internally-managed instances, the risk is lower. The availability of vendor patches for three concurrent versions (2026.1.2, 2026.2.1, 2026.3.0-latest.1) suggests the vendor responded promptly, reducing the window of exposure for patched deployments.

Exploit ScenarioDerived

An authenticated user (such as a disgruntled employee or competitor with a free trial account) logs into a multi-tenant Discourse instance and systematically requests AI metadata endpoints with sequential or enumerated identifiers (e.g., /api/ai-personas/1, /api/ai-personas/2, etc.) without requiring elevated privileges or user interaction. The attacker retrieves unredacted credit allocations and usage statistics for AI personas and LLM models across the entire organization, discovering that competitors' accounts or other departments have significantly higher AI resource budgets, enabling corporate espionage or revealing strategic priorities. Because the vulnerability requires only network access and a valid login (realistic in a public-facing discussion forum), and the CVSS attack complexity is low, exploitation is trivial and requires minimal technical sophistication.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

An Insecure Direct Object Reference (IDOR) vulnerability in Discourse allows any authenticated user to access restricted metadata about AI personas, features, and LLM models by directly referencing their identifiers, exposing sensitive information including credit allocations and usage statistics. The vulnerability affects Discourse versions prior to 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, and requires only low-privilege access (any logged-in user account) over the network. While the CVSS score of 5.3 indicates low confidentiality impact with no integrity or availability impact, this represents a clear information disclosure risk that could enable unauthorized tracking of AI resource consumption and usage patterns.

RemediationAI

Upgrade Discourse to version 2026.3.0-latest.1, 2026.2.1, or 2026.1.2 or later, depending on your current version track, as these versions contain the authorization validation patch (see vendor advisory at https://github.com/discourse/discourse/security/advisories/GHSA-3cvr-pm4c-hx96). For deployments unable to patch immediately, disable the AI plugin through the Discourse admin settings panel to eliminate the attack surface entirely. If the AI plugin must remain enabled pending patching, implement network-level access controls to restrict access to Discourse to trusted users and networks, configure authentication to require strong credentials and multi-factor authentication where possible, and monitor API access logs for suspicious enumeration patterns targeting AI metadata endpoints. Patching should be prioritized as the permanent remediation given the ease of exploitation and the sensitive nature of the exposed data.

Affected VersionsENISA

discourse = 2026.3.0-latest
discourse 2026.1.0-latest, < 2026.1.2
discourse 2026.2.0-latest, < 2026.2.1

Affected Packages

euvd discourse no fix
euvd discourse_2026_1_0_latest fix: 2026.1.2
euvd discourse_2026_2_0_latest fix: 2026.2.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 3 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability is rooted in CWE-639 (Authorization Bypass Through User-Controlled Key), a class of authorization flaws where an application fails to properly validate that a user has permission to access objects they reference directly. In Discourse's context, the AI plugin exposes API endpoints that accept identifiers for AI personas, LLM models, and feature configurations without performing adequate authorization checks beyond simple authentication status. The affected technology involves Discourse's Ruby on Rails-based backend and its AI plugin components, which fail to enforce object-level access controls on metadata endpoints. An attacker can enumerate or guess identifiers and retrieve associated metadata without additional privileges beyond a valid user session, bypassing intended access restrictions on credit allocations and usage telemetry data that should be restricted to administrators or specific role holders.

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

GitHub Advisory PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
2026.1.2,2026.2.1
CVE Published
Mar 20, 2026 - 04:16 nvd
MEDIUM 4.3

DescriptionGitHub Advisory

Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, there is an Insecure Direct Object Reference (IDOR) vulnerability that allows any authenticated user to access metadata about AI personas, features, and LLM models by providing their identifiers. This information includes credit allocations and usage statistics which are not intended to be public. The attack is performed over the network, requires low privileges (any logged-in user), and results in a low impact on confidentiality with no impact on integrity or availability. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. To work around this issue, disable AI plugin or upgrade to a patched version.

Executive ViewAI

Why It Matters

Organizations using Discourse should be aware of moderate risk from CVE-2026-32114, a IDOR vulnerability rated CVSS 4.3. Exploitation could compromise the security of affected deployments. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Low
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2025-48954 HIGH POC
8.1 Jun 25

Discourse versions prior to 3.5.0.beta6 contain a reflected cross-site scripting (XSS) vulnerability in social login fun

CVE-2022-46162 CRITICAL POC
9.8 Nov 30

discourse-bbcode is the official BBCode plugin for Discourse. Rated critical severity (CVSS 9.8), this vulnerability is

CVE-2026-27934 HIGH POC
8.7 Mar 19

Unauthorized information disclosure in Discourse discussion platform versions prior to 2026.3.0-latest.1, 2026.2.1, and

CVE-2024-47773 HIGH POC
8.2 Oct 08

Discourse is an open source platform for community discussion. Rated high severity (CVSS 8.2), this vulnerability is rem

CVE-2026-26265 HIGH POC
7.5 Feb 26

Discourse versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 contain an insecure direct object reference (IDOR) in the

CVE-2021-3138 HIGH POC
7.5 Jan 14

In Discourse 2.7.0 through beta1, a rate-limit bypass leads to a bypass of the 2FA requirement for certain forms. Rated

CVE-2026-26077 MEDIUM POC
6.5 Feb 26

Unauthenticated attackers can submit forged webhook payloads to multiple email provider integrations in Discourse versio

CVE-2023-38706 MEDIUM POC
6.5 Sep 15

Discourse is an open-source discussion platform. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploi

CVE-2024-53991 MEDIUM POC
5.9 Dec 19

Discourse is an open source platform for community discussion. Rated medium severity (CVSS 5.9), this vulnerability is r

CVE-2025-48877 CRITICAL
9.8 Jun 09

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

CVE-2023-47121 CRITICAL
9.8 Nov 10

Discourse is an open source platform for community discussion. Rated critical severity (CVSS 9.8), this vulnerability is

CVE-2022-39355 CRITICAL
9.8 Oct 26

Discourse Patreon enables syncronization between Discourse Groups and Patreon rewards. Rated critical severity (CVSS 9.8

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy