Description
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.
References5
- github.com/discourse/discourse/commit/0953b31f5c2949d7d6ab5f6dc…
- github.com/discourse/discourse/commit/3fc2bad6cdca47b00958330d1…
- github.com/discourse/discourse/commit/dde8bc4fb6200139f5eff7e10…
- github.com/discourse/discourse/commit/ed6f83f123d1a4c6c6c7e64c8…
- github.com/discourse/discourse/security/advisories/GHSA-f9jx-vv…
Metrics
- CVSS 3.1
-
7.7
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N - EPSS — exploit probability
- 0% percentile: 36 · as of 11 November 2026
- CWE
- CWE-79
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.