Discourse up to 2026.1.3/2026.3.0/2026.4.0 authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Discourse up to 2026.1.3/2026.3.0/2026.4.0 and classified as problematic. This vulnerability affects unknown code. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2026-33514. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Discourse up to 2026.1.3/2026.3.0/2026.4.0. This affects an unknown part. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:
Discourse 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, an authenticated user on a Discourse instance with the form templates feature enabled can read the name and structured content of form templates that are intended exclusively for categories they are not authorized to access. Impact is limited to disclosure of site configuration metadata. This issue has been fixed in versions 2026.1.4, 2026.3.1, 2026.4.1 and 2026.5.0-latest.1.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-33514 since 03/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 2026.1.4, 2026.3.1, 2026.4.1 or 2026.5.0-latest.1 eliminates this vulnerability. Applying the patch ae5c9570fb918442c4d96abc83c1e7e169909b02 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202605-4260). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Discourse 2026.1.4/2026.3.1/2026.4.1/2026.5.0-latest.1
Patch: ae5c9570fb918442c4d96abc83c1e7e169909b02
Timeline
03/20/2026 CVE reserved05/19/2026 Advisory disclosed
05/19/2026 VulDB entry created
05/20/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-w6g7-p2p9-2m5h
Status: Confirmed
CVE: CVE-2026-33514 (🔒)
GCVE (CVE): GCVE-0-2026-33514
GCVE (VulDB): GCVE-100-364521
CNNVD: CNNVD-202605-4260 - Discourse 安全漏洞
Entry
Created: 05/19/2026 07:13Updated: 05/20/2026 19:05
Changes: 05/19/2026 07:13 (68), 05/20/2026 19:05 (6)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.