dbcve.org
DiscourseApplication

CVE-2026-44783

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 2026.1.0 / 2026.1.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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.4, 2026.3.0-latest to before 2026.3.1, and 2026.4.0-latest to before 2026.4.1, a flaw in how replies to whisper posts are handled allows authenticated users outside the groups configured in whispers_allowed_groups to post into a topic's staff-only whisper channel. The injected content is visible to whisperers (typically staff) alongside legitimate whispers. Only sites that have whispers enabled are affected. This issue has been patched in versions 2026.1.4, 2026.3.1, 2026.4.1, and 2026.5.0-latest.1.

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

A flaw in Discourse's whisper reply handling allows authenticated users not in whispers_allowed_groups to post into staff-only whisper channels. When users reply to whisper posts, the system fails to properly validate group membership, allowing unauthorized content injection visible to staff users.

MitigationUpgrade Discourse to version 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1. If immediate upgrade is not feasible, consider disabling whispers until the patch can be applied.

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.0, < 2026.1.4>= 2026.3.0, < 2026.3.1>= 2026.4.0, < 2026.4.1= 2026.5.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Identify installed Discourse version
    Check the Discourse admin dashboard under /admin/about or inspect the VERSION file in the Discourse installation directory
    Affected if The installed version falls into any of the affected ranges: < 2026.1.0, 2026.1.0 to < 2026.1.4, 2026.3.0 to < 2026.3.1, 2026.4.0 to < 2026.4.1, or exactly 2026.5.0
  2. Confirm whispers feature is enabled
    Navigate to Discourse admin panel, go to Settings > Plugins > whispers, or check the site settings for enable_whispers or whispers_allowed_groups configuration
    Affected if Whispers are enabled and the whispers_allowed_groups setting is configured with any group values
  3. Verify group membership validation configuration
    Review the whispers_allowed_groups site setting in the Discourse admin interface at /admin/site_settings/category/whispers
    Affected if The setting allows any non-staff user group to interact with whispers, or if the validation logic can be bypassed for reply actions

If your Discourse version is affected and whispers are enabled with configured allowed groups, your installation is vulnerable to unauthorized users posting into staff-only whisper channels.

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 2026.1.0 / 2026.1.4 / 2026.3.1 or later
Fixed in 2026.1.02026.1.42026.3.1
Interim mitigation

Upgrade Discourse to version 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1. If immediate upgrade is not feasible, consider disabling whispers until the patch can be applied.

Recommended fix High confidence

2026.5.0-latest.1 (or latest stable 2026.x release)

  1. 1. Identify your current Discourse version by checking the /admin dashboard or running `git log` in your Discourse installation directory
  2. 2. Based on your current version branch, upgrade to a patched version: if on 2026.1.x, upgrade to 2026.1.4 or later; if on 2026.3.x, upgrade to 2026.3.1 or later; if on 2026.4.x, upgrade to 2026.4.1 or later; otherwise upgrade to the latest stable release (2026.5.0-latest.1 or newer)
  3. 3. Follow standard Discourse upgrade procedures: back up your database, stop the application, run `./launcher rebuild app`, then verify the upgrade completed successfully
  4. 4. After upgrade, verify that whispers functionality still works correctly for authorized users in the configured whispers_allowed_groups
  5. 5. Review admin logs to confirm no unauthorized whisper posts were injected during the vulnerability window

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

Fix this in Discourse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44783 — 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-44783 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