CVE-2026-34154
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 · uneditedDiscourse is an open-source discussion platform. In versions prior to 2026.1.4, 2026.3.1, 2026.4.1 and 2026.5.0-latest.1, a vulnerability in the discourse-subscriptions plugin allows users to gain access to subscription-gated groups without completing payment. This issue has been fixed 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 confidenceThe discourse-subscriptions plugin contains an authorization bypass vulnerability where users can access subscription-gated groups without completing payment. This is a broken access control issue in the group membership logic that should enforce payment verification before granting group access.
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>= 2026.1.0, < 2026.1.4>= 2026.3.0, < 2026.3.1>= 2026.4.0, < 2026.4.1= 2026.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify discourse-subscriptions plugin is enabledCheck your Discourse admin panel under Plugins or examine the plugin configuration files to confirm the discourse-subscriptions plugin is installed and activeAffected if The plugin is installed and enabled on the instance
-
Determine installed Discourse versionAccess your Discourse admin dashboard and locate the version information, or check the version file in your Discourse installation directoryAffected if The installed version falls within one of these ranges: >= 2026.1.0 and < 2026.1.4, >= 2026.3.0 and < 2026.3.1, >= 2026.4.0 and < 2026.4.1, or equals 2026.5.0
-
Identify subscription-gated groupsReview your Discourse group settings in the admin panel to see which groups are configured as subscription-gated (groups that require payment to access)Affected if There are groups configured that require a paid subscription for membership
-
Check user membership in subscription-gated groupsExamine user group memberships, particularly for authenticated users who may have been added to subscription-gated groups without proper payment verificationAffected if Users have access to subscription-gated groups and there is no record of completed payment for those memberships
You are affected if the discourse-subscriptions plugin is enabled AND your Discourse version is one of the affected versions AND you have subscription-gated groups configured in your environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.1.42026.3.12026.4.1
Upgrade Discourse to versions 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1 which contain the fix for this vulnerability. Verify that subscription-gated groups properly enforce payment requirements after upgrading.
2026.5.0-latest.1
- Upgrade Discourse to version 2026.5.0-latest.1 (or 2026.1.4, 2026.3.1, or 2026.4.1 depending on your current branch)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34154 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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