HTML injection in Discourse solved posts via display names
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · GHSA-48h6-hpp2-357h. Fix status from GitHub.
Summary
Discourse versions before adba4d9 are affected. When a topic is solved and the display_name_on_posts setting is enabled, user display names containing HTML are not escaped and the HTML is rendered. An attacker with low privileges can inject this HTML, but a user must interact with the page for it to take effect, and the impact is limited to low confidentiality loss.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact User's names (not usernames) with html will may result in HTML injection when a topic is solved and the site has the `display_name_on_posts` setting enabled. ### Workarounds Disable the `display_name_on_posts` setting.
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 (discourse) | < adba4d9 | — | No fix listed | GHSA-48h6-hpp2-357h |
- discourse (discourse) Vendor— Affected < adba4d9 Fixed in — No fix listed GHSA-48h6-hpp2-357h
Remediation
The sources list no fixed version for Discourse. Disable the display_name_on_posts setting as a workaround.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Timeline
- 2026-11-12 Threatist record created from GHSA-48h6-hpp2-357h
- 2026-11-12 Alias added: CVE-2025-53016
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences