HTML injection in personal message notification emails via participant names
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- None · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · GHSA-g8gp-vp9x-6jqq. Fix status from GitHub. Impact type from CWE-79.
Summary
Discourse lists the other participants of a personal message as links in its notification emails. User and group names were inserted without sanitization (CWE-79), so HTML or Markdown in a name rendered as markup in emails sent to other participants, letting an attacker add images, restyle the email or insert misleading links. Group owners can set a group full name, so this works with default settings for any group invited to a personal message, while a user's full name is used only when prioritize_username_in_ux is disabled. Sites that added %{topic_title} to customized email header, footer or preview text were also affected through topic titles.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact Notification emails for personal messages list the other participants as links. User and group names were inserted into these emails without sanitization, so a name containing HTML or Markdown was rendered as markup in the emails other participants receive, for example to add images, restyle the email or insert misleading links. A group full name can be set by group owners, so this works with default settings for any group that is invited to a personal message. A user's own full name is only used when `prioritize_username_in_ux` is disabled. Sites where an admin customized the email header, footer or preview text to include `%{topic_title}` were also affected through topic titles. ### Patches The email snippets are now sanitized and participant names are escaped. Fixed in `2026.11.0-latest`. Fixed release versions will be added after the fix and backports are released. ### Workarounds Keep `prioritize_username_in_ux` enabled, and avoid `%{topic_title}` in customized email header, footer or preview texts. There is no workaround for group full names other than reviewing the full names of groups with non-staff owners. ### References None.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | Discourse | — | 2026.11.0-latest.1 | Patch available | GHSA-g8gp-vp9x-6jqq |
| — | Discourse | >= 2026.10.0-latest | 2026.10.1 | Patch available | GHSA-g8gp-vp9x-6jqq |
| — | Discourse | >= 2026.9.0-latest | 2026.9.2 | Patch available | GHSA-g8gp-vp9x-6jqq |
| — | Discourse | >= 2026.7.0-latest | 2026.7.5 | Patch available | GHSA-g8gp-vp9x-6jqq |
- Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-g8gp-vp9x-6jqq
- Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-g8gp-vp9x-6jqq
- Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-g8gp-vp9x-6jqq
- Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-g8gp-vp9x-6jqq
Remediation
Upgrade to a fixed release: 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5. The email snippets are now sanitized and participant names are escaped. Until upgrading, keep prioritize_username_in_ux enabled, avoid %{topic_title} in customized email header, footer or preview texts, and review the full names of groups with non-staff owners, since no other workaround exists for group full names.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-g8gp-vp9x-6jqq Discourse Fixed in 2026.11.0-latest.1 Advisory →
- Fix · GHSA-g8gp-vp9x-6jqq Discourse Fixed in 2026.10.1 Advisory →
- Fix · GHSA-g8gp-vp9x-6jqq Discourse Fixed in 2026.9.2 Advisory →
- Fix · GHSA-g8gp-vp9x-6jqq Discourse Fixed in 2026.7.5 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-g8gp-vp9x-6jqq
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences