Skip to content
Fencer Intel
high 8.2

CVE-2024-47773 json

Anonymous cache poisoning via XHR requests in Discourse

published 2y ago modified 2mo ago also BIT-discourse-2024-47773 , EUVD-2024-42683 , GHSA-58vv-9j8h-hw2v

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • bitnami discourse 3.3.2
  • discourse discourse 3.3.2

Is CVE-2024-47773 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-52358)

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

1.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • EDB-52358 Discourse 3.2.x - Anonymous Cache Poisoning webapps, 2025-07-08

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
OSV 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Affected packages

ecosystem package affected fixed in
bitnami discourse
<3.3.2
3.3.2

Affected products

  • discourse discourse

Classification

Weakness
  • CWE-610 Externally Controlled Reference to a Resource in Another Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.