Discourse up to 2026.1.1/2026.2.0/2026.3.0-latest authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Discourse up to 2026.1.1/2026.2.0/2026.3.0-latest. The affected element is an unknown function. Performing a manipulation results in authorization. This vulnerability is cataloged as CVE-2026-33408. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Discourse up to 2026.1.1/2026.2.0/2026.3.0-latest. This affects some unknown processing. 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. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, moderators were able to see the first 40 characters of post edits in PMs and private categories. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-33408 since 03/19/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 2026.1.2 or 2026.2.1 eliminates this vulnerability. Applying the patch 3bf3793a708662716c0a4eaf64ae091abe71ab4c 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.4VulDB Meta Temp Score: 2.3
VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 2.7
NVD Vector: 🔒
CNA Base Score: 2.2
CNA Vector (GitHub_M): 🔒
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.2/2026.2.1
Patch: 3bf3793a708662716c0a4eaf64ae091abe71ab4c
Timeline
03/19/2026 CVE reserved03/20/2026 Advisory disclosed
03/20/2026 VulDB entry created
03/25/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-wf9r-386h-g29c
Status: Confirmed
CVE: CVE-2026-33408 (🔒)
GCVE (CVE): GCVE-0-2026-33408
GCVE (VulDB): GCVE-100-351819
Entry
Created: 03/20/2026 07:23Updated: 03/25/2026 08:33
Changes: 03/20/2026 07:23 (65), 03/23/2026 00:51 (1), 03/25/2026 08:33 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.