Security readout for executives and security teams
Plain-English summary
This Discourse flaw could reveal which staff member created a hidden whisper post to non-staff users. The hidden post content is not described as exposed, but staff identity and activity metadata can leak. Business impact is mainly confidentiality and trust in private moderation workflows.
Executive priority
Schedule remediation in the normal security patch cycle, faster for sensitive communities or moderation-heavy forums. This is not a system takeover issue, but it can undermine private staff coordination and expose moderation activity.
Technical view
Discourse versions before 2.7.7 have two whisper metadata exposure bugs. Non-staff personal message participants may see the creator of a staff whisper, and deleting a last post can make a preceding whisper creator appear as the topic last poster. The issue maps to CWE-668 and CVSS 4.3.
Likely exposure
Exposure is limited to Discourse deployments running versions earlier than 2.7.7, especially communities using staff whisper posts in personal messages or topic streams. It requires an authenticated non-staff user in the relevant context.
Exploitation context
The source bundle does not show active exploitation, and CISA KEV status is false. The attack complexity is low and network reachable, but the documented impact is limited to disclosure of the whisper post creator, not message content or system control.
Researcher notes
The advisory identifies two metadata leak paths tied to whisper post handling and last-poster state. Avoid assuming broader private message disclosure; the supplied evidence only supports creator identity exposure. Fixed behavior is represented by the linked Discourse commits and version 2.7.7 boundary.
Mitigation direction
- Upgrade affected Discourse instances to version 2.7.7 or later.
- Review the GitHub advisory for branch-specific vendor guidance.
- If upgrade is delayed, ask Discourse for supported temporary controls.
- Treat exposed staff identity metadata as a potential confidentiality incident.
Validation and detection
- Inventory Discourse versions and flag any instance below 2.7.7.
- Confirm whether staff whisper posts are used in personal messages or topics.
- After patching, verify non-staff users cannot see whisper creator metadata.
- Review relevant moderation workflows for possible identity exposure.
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-668: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2021-32788 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
- 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:L/I:N/A:N
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:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/discourse/discourse/security/advisories/GHSA-v6xg-q577-vc92CVE reference · x_refsource_CONFIRM
- https://github.com/discourse/discourse/commit/680024f9071b7696e5a444a58791016c6dc1f1e5CVE reference · x_refsource_MISC
- https://github.com/discourse/discourse/commit/dbdf61196d9e964e8823793d2e7f856595fea4d9CVE reference · x_refsource_MISC
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.
Exposure of Resource to Wrong Sphere
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.