CVERadar
HIGH · CVSS 3.1 8.2Exploit-DBEPSS 1.66% (p77)Threat level 48

CVE-2024-47773: CVE-2024-47773: Discourse is an open source platform for community discussion. An attacker can make severa…

discourse · discourse · NVD published 2024-10-08 · posted 2025-07-08 · last modified 2026-06-17

What it 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.

WeaknessCWE-610
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L (source: [email protected])
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2025-07-08 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

Exploit-DB

  • EDB-52358: Discourse 3.2.x - Anonymous Cache Poisoning (2025-07-08)

Sources: Exploit-DB (OffSec).

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

Fixed versions

  • discourse discourse: upgrade to 3.3.2 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources