Security readout for executives and security teams
Plain-English summary
A trusted Discourse user at Trust Level 4 could create or publish topics into staff-only categories they should not access. This is a limited authorization bypass with low severity, but it may expose internal moderation workflows or create unwanted staff-area content.
Executive priority
Treat as routine patching unless staff-only categories contain sensitive operational content or TL4 membership is broad. The business risk is limited but real for confidentiality and integrity of internal forum areas.
Technical view
Discourse before 2025.12.2, 2026.1.1, and 2026.2.0 allows TL4 users to use the publish_to_category topic timer to publish into staff-only categories without proper authorization checks. The issue is classified as CWE-863 and has CVSS 4.0 score 1.2.
Likely exposure
Exposure is limited to Discourse instances running affected versions and having TL4 users. Anonymous users and ordinary low-privilege users are not described as able to exploit this issue.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. Exploitation requires a high-privilege TL4 account and network access to the Discourse site.
Researcher notes
The vulnerability is an authorization check bypass in a topic timer path, not a general staff-category access flaw. Evidence provided does not include proof-of-concept details, exploit telemetry, or workaround guidance.
Mitigation direction
- Upgrade Discourse to 2025.12.2, 2026.1.1, 2026.2.0, or later applicable release.
- Prioritize sites with many TL4 users or sensitive staff-only categories.
- No workaround is named in the advisory; follow vendor guidance if upgrade is delayed.
Validation and detection
- Confirm the running Discourse version is not in the affected version ranges.
- Review the site for TL4 users who can create or schedule topic timers.
- Check staff-only categories for unexpected topics created or published by TL4 users.
- Monitor the GitHub advisory for any updated remediation or detection guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2026-28227 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 1.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
1.2LowVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/discourse/discourse/security/advisories/GHSA-m49w-78mh-87jpCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.