Discourse up to 3.1.0/3.2.0.beta1 POST Request information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Discourse up to 3.1.0/3.2.0.beta1. This issue affects some unknown processing of the component POST Request Handler. Executing a manipulation can lead to information disclosure. This vulnerability is handled as CVE-2023-45131. The attack can be executed remotely. Additionally, an exploit exists. You should upgrade the affected component.
Details
A vulnerability has been found in Discourse up to 3.1.0/3.2.0.beta1 and classified as problematic. This vulnerability affects some unknown functionality of the component POST Request Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
Discourse is an open source platform for community discussion. New chat messages can be read by making an unauthenticated POST request to MessageBus. This issue is patched in the 3.1.1 stable and 3.2.0.beta2 versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.
The weakness was released 10/17/2023 as GHSA-84gf-hhrc-9pw6. The advisory is shared for download at github.com. This vulnerability was named CVE-2023-45131 since 10/04/2023. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 3.1.1 or 3.2.0.beta2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (52375). Once again VulDB remains the best source 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: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Discourse 3.1.1/3.2.0.beta2
Timeline
10/04/2023 🔍10/17/2023 🔍
10/17/2023 🔍
07/27/2025 🔍
Sources
Product: github.comAdvisory: GHSA-84gf-hhrc-9pw6
Status: Confirmed
CVE: CVE-2023-45131 (🔍)
GCVE (CVE): GCVE-0-2023-45131
GCVE (VulDB): GCVE-100-242356
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/17/2023 08:12Updated: 07/27/2025 04:09
Changes: 10/17/2023 08:12 (50), 07/27/2025 04:09 (25)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.