Security readout for executives and security teams
Plain-English summary
This is a low-severity privacy and abuse-control issue in Discourse direct messages. A logged-in user could add someone to an existing DM channel even if that person blocked, ignored, or muted them. It bypasses recipient communication preferences, but does not indicate system takeover, data destruction, or broad compromise.
Executive priority
Treat as a routine but privacy-relevant update. Prioritize for communities where harassment controls, moderation trust, or regulated user communications matter. It is not presented as an emergency infrastructure risk.
Technical view
Discourse before 2025.12.2, 2026.1.1, and 2026.2.0 has an access-control flaw in Chat::AddUsersToChannel. PM restrictions are enforced when creating a DM channel, but not when adding members later. The advisory maps this to CWE-284 and CVSS 4.0 score 1.3 low.
Likely exposure
Exposure is limited to Discourse sites running affected versions with chat or DM functionality where authenticated users can add members to DM channels. The main impact is unwanted contact and preference bypass, not infrastructure compromise.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires a logged-in user and targets the application’s DM membership workflow rather than server code execution.
Researcher notes
Evidence is limited to the CVE record and Discourse GitHub advisory. The issue is a logic authorization gap between DM creation and later member addition. No workaround, exploit publication, or active exploitation is cited in the provided sources.
Mitigation direction
- Upgrade Discourse to 2025.12.2, 2026.1.1, 2026.2.0, or later as applicable.
- Review the GitHub advisory for any newly published operational guidance.
- If immediate upgrade is delayed, monitor DM abuse reports closely; no workaround is listed.
Validation and detection
- Confirm the running Discourse version against the fixed versions listed in the advisory.
- Review user reports or moderation logs for unwanted DM channel additions.
- Verify communication-preference controls after upgrading in a test or staging environment.
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-284: 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-27152 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.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
1.3LowVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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-f8ff-pxg3-7967CVE 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.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.