Discourse up to 2026.1.1/2026.2.0/2026.3.0-latest Private Message post_edits information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Discourse up to 2026.1.1/2026.2.0/2026.3.0-latest and classified as problematic. This impacts an unknown function of the file /admin/reports/post_edits of the component Private Message Handler. Performing a manipulation results in information disclosure. This vulnerability is identified as CVE-2026-33394. 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.1/2026.2.0/2026.3.0-latest. This affects an unknown part of the file /admin/reports/post_edits of the component Private Message Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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, the Post Edits admin report (/admin/reports/post_edits) leaked the first 40 characters of raw post content from private messages and secure categories to moderators who shouldn't have access. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-33394 since 03/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
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.
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: 🔍
CVSSv3
VulDB Meta Base Score: 2.7VulDB Meta Temp Score: 2.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 2.7
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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-wxvr-pm5c-829p
Status: Confirmed
CVE: CVE-2026-33394 (🔒)
GCVE (CVE): GCVE-0-2026-33394
GCVE (VulDB): GCVE-100-351921
Entry
Created: 03/20/2026 08:08Updated: 03/25/2026 05:14
Changes: 03/20/2026 08:08 (68), 03/25/2026 05:14 (1)
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.