Discourse up to 3.3.1/3.4.0.beta1 DISCOURSE_DISABLE_ANON_CACHE external reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Discourse up to 3.3.1/3.4.0.beta1. It has been rated as critical. The affected element is an unknown function. This manipulation of the argument DISCOURSE_DISABLE_ANON_CACHE causes external reference. The identification of this vulnerability is CVE-2024-47773. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in Discourse up to 3.3.1/3.4.0.beta1 and classified as critical. Affected by this vulnerability is an unknown function. The manipulation of the argument DISCOURSE_DISABLE_ANON_CACHE with an unknown input leads to a external reference vulnerability. The CWE definition for the vulnerability is CWE-610. The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere. As an impact it is known to affect integrity, and availability. The summary by CVE is:
Discourse is an open source platform for community discussion. An attacker can make several XHR requests until the cache is poisoned with a response without any preloaded data. This issue only affects anonymous visitors of the site. This problem has been patched in the latest version of Discourse. Users are advised to upgrade. Users unable to upgrade should disable anonymous cache by setting the `DISCOURSE_DISABLE_ANON_CACHE` environment variable to a non-empty value.
The advisory is shared at github.com. This vulnerability is known as CVE-2024-47773 since 09/30/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 3.3.2 or 3.4.0.beta2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (52358). 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: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.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: External referenceCWE: CWE-610
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.3.2/3.4.0.beta2
Timeline
09/30/2024 🔍10/08/2024 🔍
10/08/2024 🔍
08/27/2025 🔍
Sources
Product: github.comAdvisory: GHSA-58vv-9j8h-hw2v
Status: Confirmed
CVE: CVE-2024-47773 (🔍)
GCVE (CVE): GCVE-0-2024-47773
GCVE (VulDB): GCVE-100-279769
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/08/2024 20:48Updated: 08/27/2025 04:17
Changes: 10/08/2024 20:48 (63), 07/09/2025 20:49 (12), 08/27/2025 04:17 (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.