Discourse
Discourse: Stored oEmbed HTML injection via allowed iframe
Discourse is an open-source discussion platform. Prior to 2026.9.0, 2026.8.1, 2026.7.3, and 2026.1.9, oEmbed processing treated an entire attacker-controlled HTML fragment as trusted when the fragment contained an iframe whose source matched the configured allowlist. A user with posting permission who controlled a public webpage and its oEmbed response could combine an allowlisted iframe with unrelated sibling HTML or CSS, causing stored visual overlays or other styled content to appear in post content and enabling misleading or fraudulent user interfaces. Exploitation requires a posting account, control of the fetched webpage and oEmbed response, and an allowlisted iframe source. The issue affects content integrity but does not expose restricted data, disrupt availability, or require interaction with Discourse Content Security Policy. This issue is fixed in versions 2026.9.0, 2026.8.1, 2026.7.3, and 2026.1.9.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2026.1.9
- >= 2026.7.0-latest, < 2026.7.3
- >= 2026.8.0-latest, < 2026.8.1
- >= 2026.9.0-latest, < 2026.9.0
Fixed in 2026.1.9, 2026.7.3, 2026.8.1, 2026.9.0
Mitigation
Upgrade discourse to 2026.1.9 or 2026.7.3 or 2026.8.1 or 2026.9.0 or later.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| sl4x0/autheo-cve-2026-91159-poc | 30 Sep 2026 −14 d | 0 | Informational · write-up |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.