LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26973: Discourse doesn't scope reviewable notes to user-visible reviewables

Discourse is an open source discussion platform. Versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 have an IDOR (Insecure Direct Object Reference) in `ReviewableNotesController`. When `enable_category_group_moderation` is enabled, a user belonging to a category moderation group can create or delete their own notes on **any** reviewable in the system, including reviewables in categories they do not moderate. The controller used an unscoped `Reviewable.find` and the `ensure_can_see` guard only checked whether the user could access the review queue in general, not whether they could access the specific reviewable. Only instances with `enable_category_group_moderation` enabled are affected. Staff users (admins/moderators) are not impacted as they already have access to all reviewables. The issue is patched in versions 2025.12.2, 2026.1.1, and 2026.2.0 by scoping the reviewable lookup through `Reviewable.viewable_by(current_user)`. As a workaround, disable the `enable_category_group_moderation` site setting. This removes the attack surface as only staff users will have access to the review queue.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Certain Discourse sites let category moderators add or delete their own review notes on review items outside their assigned categories. This is a permissions scoping flaw, not a full system compromise. Business impact is limited integrity risk in moderation workflows, mainly where category group moderation is enabled.

Executive priority

Treat as a scheduled but timely fix for affected Discourse communities using delegated category moderation. Prioritize faster if moderation integrity, abuse handling, or private category workflows are business-critical.

Technical view

CVE-2026-26973 is an IDOR/authorization flaw in Discourse ReviewableNotesController. The controller used an unscoped Reviewable.find, while ensure_can_see checked general review queue access rather than access to the specific reviewable. Patched versions scope lookup through Reviewable.viewable_by(current_user). CVSS is 4.3, PR:L, UI:N, integrity-only impact.

Likely exposure

Exposure is limited to Discourse instances running affected versions before 2025.12.2, 2026.1.1, or 2026.2.0 with enable_category_group_moderation enabled. Staff users are not meaningfully affected because they already have access to all reviewables.

Exploitation context

A logged-in user in a category moderation group could create or delete their own notes on reviewables in categories they do not moderate. The source bundle does not report active exploitation, and the CVE is not marked in KEV.

Researcher notes

The key security boundary is per-reviewable visibility for category moderators. The fix described is scoping object lookup through Reviewable.viewable_by(current_user). Evidence provided does not indicate confidentiality or availability impact, public exploitation, or affected non-Discourse products.

Mitigation direction

  • Upgrade Discourse to 2025.12.2, 2026.1.1, 2026.2.0, or later as applicable.
  • If immediate upgrade is not possible, disable enable_category_group_moderation.
  • Review vendor advisory for deployment-specific guidance before changing moderation settings.

Validation and detection

  • Confirm the running Discourse version is not below the patched releases.
  • Check whether enable_category_group_moderation is enabled.
  • Review category moderator group membership for users with review queue access.
  • After patching, verify reviewable note access is limited to viewable reviewables.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26973 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-26973Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
discoursediscourse< 2025.12.2, >= 2026.1.0-latest, < 2026.1.1, >= 2026.2.0-latest, < 2026.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.