dbcve.org
DiscourseApplication

CVE-2026-34947

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-03
Fix available
A fix is available. Upgrade to after 2026.2.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Staged user custom fields and usernames are inadvertently exposed on public invite pages without requiring email verification, allowing unauthorized disclosure of user information.

MitigationUpgrade Discourse to version 2026.1.3, 2026.2.2, or 2026.3.0 to patch the information disclosure vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DiscourseApplication
Affected:>= 2026.1.0, <= 2026.1.2>= 2026.2.0, <= 2026.2.1= 2026.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine your installed Discourse version
    Log into the Discourse admin panel and navigate to /admin/about, or check the version file in your Discourse installation directory (VERSION file in the discourse root)
    Affected if The installed version is >= 2026.1.0 and <= 2026.1.2, OR >= 2026.2.0 and <= 2026.2.1, OR equals 2026.3.0
  2. Verify if invite functionality is enabled
    In the Discourse admin panel, go to Settings > Users > Invites and check if 'enable invites' or similar invite-related settings are turned on, or query the site_settings table for invite-related flags
    Affected if Invite functionality is enabled in the site settings
  3. Confirm if invite pages are publicly accessible
    Check the Discourse site settings for 'invite_passthrough' or 'allow_public_invites' settings, or attempt to access the /invites route on your forum without authentication
    Affected if Invite pages are accessible to unauthenticated (public) users
  4. Check for staged user accounts with profile data
    Query the database: SELECT id, username, email, staged FROM users WHERE staged = true; then check for custom profile fields associated with these users in the user_custom_fields table
    Affected if There are staged (incomplete) user accounts in the system with custom profile fields populated

You are affected if your Discourse version falls within the affected ranges AND invite functionality is enabled and publicly accessible AND staged users with profile information exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2026.2.1
Interim mitigation

Upgrade Discourse to version 2026.1.3, 2026.2.2, or 2026.3.0 to patch the information disclosure vulnerability.

Recommended fix High confidence

2026.1.3 (for 2026.1.x branch) or 2026.2.2 (for 2026.2.x branch) or 2026.3.0 (for 2026.3.x branch)

  1. Identify the currently installed Discourse version using the admin dashboard or discourse version command
  2. If running 2026.1.0-2026.1.2, upgrade to 2026.1.3
  3. If running 2026.2.0-2026.2.1, upgrade to 2026.2.2
  4. If running 2026.3.0, upgrade to 2026.3.0 (the fixed release)
  5. After upgrade, verify the patch by testing that invite pages no longer expose staged user custom fields or usernames without email verification

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Discourse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data