Skip to main content

Discourse EUVDEUVD-2026-42740

| CVE-2026-45780 MEDIUM
Information Exposure (CWE-200)
2026-07-09 security-advisories@github.com
4.3
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Access Discourse topic URL with private event
  2. Delivery
    Fetch topic JSON response via browser or API
  3. Exploit
    EventSerializer returns uninspected private metadata
  4. Execution
    Extract invited group names and sample invitee usernames
  5. Impact
    Use membership data for reconnaissance or social engineering

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the target Discourse installation has event functionality enabled and that at least one topic contains a private event with a configured invitee list. The disclosure is triggered passively by any user who can view the topic - on open forums this includes unauthenticated visitors; on restricted forums it includes any account with topic-read permission. No elevated privileges, special configuration, or user interaction is required beyond topic-read access. The limiting factor is deployment context: Discourse instances without event functionality, or with no topics using private invitee lists, have no exposure to this specific flaw. The leaked data is scoped to event invitation metadata (group names, sample invitees, attendance statistics) and does not include full user account data, private messages, or non-event content.

Impact

The CVSS 5.3 Medium score with vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N accurately reflects the risk profile: trivial access conditions (no authentication, no complexity, no user interaction) but bounded low-confidentiality impact. Real-world priority is moderate and context-dependent - Discourse deployments that host private events with restricted invitee lists face genuine privacy exposure, as group membership and attendee rosters can be used for targeted social engineering or to enumerate organizational structure. EPSS data was not provided in the available intelligence, so exploitation probability cannot be quantified beyond the CVSS vector. The vulnerability is not listed in CISA KEV and no public POC has been identified, which reduces urgency compared to the low access complexity. The most meaningful risk signal is the PR:N combined with C:L: on open or semi-open forums, this is passively exploitable by any visitor without any special tooling.

Exploit ScenarioDerived

An unauthenticated visitor or low-privilege member on an open Discourse forum navigates to a topic containing a private event and retrieves the topic's JSON payload - either via the standard Discourse API endpoint or by inspecting browser network traffic. The EventSerializer returns the full private invitation metadata, including invited group names, a sample of invitee usernames, and attendance counts, without any authorization check. The attacker passively harvests organizational group membership and event attendance data without triggering any alerts or requiring any special tooling. No public exploit code has been identified, but the attack requires nothing beyond an HTTP GET request.

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

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

Alert me

AnalysisAIv1 – Jul 09, 2026

EventSerializer in Discourse improperly exposes private event invitation metadata - including invited group names, sample invitee usernames, and attendance statistics - to any user who can view the topic, regardless of their authorization to access the private invitee list. All Discourse installations prior to versions 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 are affected when event functionality is in use. No public exploit or active exploitation (CISA KEV) has been identified, but the trivial network vector (AV:N/AC:L/PR:N/UI:N) makes this passively accessible to any user - authenticated or not - with topic-read access on an open or semi-open forum.

RemediationAI

Upgrade Discourse to one of the patched releases: v2026.6.0 (stable), v2026.5.1 (beta), v2026.4.2 (beta), or v2026.1.5 (LTS), available at the respective GitHub release tags referenced in the advisory. These are vendor-confirmed patch versions with upstream commits addressing the serializer access control flaw. If immediate patching is not feasible, a compensating control is to restrict topic-view access so that only fully trusted, explicitly authorized users can read topics containing private events - this reduces the disclosure surface but limits forum openness and may conflict with community access policies. Disabling event functionality entirely eliminates the attack surface with no security trade-off, though it removes the feature. No other vendor-documented workarounds are available in the provided intelligence.

Affected VersionsENISA

discourse 2026.5.0-latest, < 2026.5.1
discourse 2026.1.0-latest, < 2026.1.5
discourse 2026.4.0-latest, < 2026.4.2

Affected Packages

euvd discourse_2026_1_0_latest fix: 2026.1.5
euvd discourse_2026_4_0_latest fix: 2026.4.2
euvd discourse_2026_5_0_latest fix: 2026.5.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

Discourse is a widely-deployed Ruby on Rails open-source discussion platform used for community forums, product support, and internal knowledge bases. The vulnerability resides in EventSerializer, the serialization layer responsible for structuring event-related data into JSON API responses for topic views. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) describes the root cause: the serializer includes private event invitation metadata - invited group names, sample invitee profiles, and attendance statistics - in the topic payload without verifying whether the requesting user is entitled to view the private invitee list. This is a missing authorization check at the serialization layer rather than a cryptographic or memory-safety flaw. The fix was applied across four commits (37969503, 4d46638, 6457ab71, 7deb4b69) addressing the same issue across multiple maintained release branches.

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

NVD PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Any user with topic-read access triggers disclosure over the network with no authentication; impact is limited to low confidentiality with no integrity or availability consequences.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

2
CVSS changed
Jul 14, 2026 - 20:52 NVD
5.3 (MEDIUM) 4.3 (MEDIUM)
Patch available
Jul 09, 2026 - 23:02 EUVD

DescriptionNVD

Discourse is an open-source discussion platform. Prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5, EventSerializer could expose invited group names, sample invitees, and attendance statistics to users who could view the topic but were not entitled to view the private event invitee list. This issue is fixed in versions 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5.

Threat Intelligence Overview

EPSS Score
0.4%
Top 68% exploitable
Prevalence
Medium
popular open-source forum platform, widely deployed but not ubiquitous
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.4%
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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
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

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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