Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess Discourse topic URL with private event
-
DeliveryFetch topic JSON response via browser or API
-
ExploitEventSerializer returns uninspected private metadata
-
ExecutionExtract invited group names and sample invitee usernames
-
ImpactUse 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
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
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
EUVD-2026-42740
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB