Skip to main content

Discourse EUVDEUVD-2026-55660

| CVE-2026-72723 MEDIUM
Missing Authorization (CWE-862)
2026-08-10 GitHub_M
5.3
CVSS 3.1 · Vendor: GitHub_M
Share

Severity by source

Vendor (GitHub_M) PRIMARY
5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI
5.3 MEDIUM

Network-accessible unauthenticated endpoint; only tag metadata disclosed, so C:L; no integrity or availability impact.

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 Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

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

Lifecycle Timeline

3
Patch available
Aug 10, 2026 - 17:03 EUVD
Source Code Evidence Fetched
Aug 10, 2026 - 16:33 vuln.today
Analysis Generated
Aug 10, 2026 - 16:33 vuln.today

DescriptionCVE.org

Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, SiteSerializer.anonymous_default_navigation_menu_tags serializes tags from SiteSetting.default_navigation_menu_tags without applying DiscourseTagging.filter_visible for the anonymous viewer. An unauthenticated user can retrieve restricted tag names and descriptions through /site.json when those tags are limited by inaccessible categories, category tag groups, or tag-group permissions. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.

AnalysisAI

Unauthorized tag enumeration in Discourse exposes restricted tag names and descriptions to unauthenticated users via the /site.json endpoint. The flaw exists in all Discourse releases prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, where the anonymous site serializer populates default navigation menu tags from SiteSettings without invoking the DiscourseTagging.filter_visible visibility guard. Attackers can trivially enumerate tag names and descriptions that administrators have restricted to specific categories, category tag groups, or tag-group permission rules, undermining Discourse's information compartmentalization model. No public exploit code or active exploitation has been identified at time of analysis.

Technical ContextAI

Discourse (CPE: cpe:2.3:a:discourse:discourse:*:*:*:*:*:*:*:*) is a Ruby on Rails-based open-source forum platform that exposes a /site.json endpoint consumed by its Ember.js frontend. The endpoint is served by SiteSerializer, which populates the anonymous_default_navigation_menu_tags field directly from SiteSetting.default_navigation_menu_tags - a site-level configuration list of tags intended to appear in the navigation menu. The root cause (CWE-862: Missing Authorization) is that this serializer path omits a call to DiscourseTagging.filter_visible, which is the standard Discourse API for applying per-viewer visibility rules to tags based on category restrictions, category_tag_groups, and tag_group permissions. The fix in PR 42091 reflects a broader refactor of the anonymous cache path in site.rb, replacing eager-loading of :tags and :tag_groups with :category_required_tag_groups, decoupling the anonymous serializer from the full unrestricted tag set.

RemediationAI

Upgrade Discourse to one of the patched versions corresponding to your release branch: 2026.1.6, 2026.5.2, 2026.6.1, or 2026.7.0. The upstream fixes are delivered across four pull requests (PRs 42091-42094) and four associated commits, all referenced in the vendor advisory at https://github.com/discourse/discourse/security/advisories/GHSA-4p6q-h74v-5j7p. If an immediate upgrade is not feasible, a partial workaround is to remove all tags from SiteSetting.default_navigation_menu_tags that are subject to category or tag-group visibility restrictions, effectively preventing any restricted tags from being eligible for inclusion in the anonymous serializer response; note this trades off navigation usability for authenticated members. There is no network-layer mitigation that can suppress /site.json exposure without breaking the Discourse frontend, as the endpoint is required for client bootstrapping.

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-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-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

CVE-2021-41163 CRITICAL
9.8 Oct 20

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

CVE-2026-27454 MEDIUM POC
5.3 Mar 19

Unauthorized access to hidden post revisions in Discourse through version enumeration allows unauthenticated users to by

Share

EUVD-2026-55660 vulnerability details – vuln.today

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