Loading vulnerability…
CVE-2024-47773 affects Discourse, an open source community discussion platform. An attacker can send multiple XMLHttpRequest (XHR) requests until the anonymous cache is poisoned with a response that lacks preloaded data. The issue impacts responses served from Discourse's anonymous caching mechanism, causing cached content for unauthenticated users to be populated with an incomplete response variant. Based on the provided information, the flaw is a cache poisoning issue affecting anonymous visitors rather than authenticated sessions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
DISCOURSE_DISABLE_ANON_CACHE environment variable to a non-empty value. This removes the vulnerable caching behavior affecting anonymous visitors.Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Python proof-of-concept exploit for CVE-2024-47773, a cache poisoning vulnerability affecting Discourse forum software. The main file, CVE-2024-47773.py, is a command-line tool that targets Discourse instances by sending multiple concurrent HTTP requests to various API endpoints as an anonymous user. The goal is to poison the cache so that subsequent anonymous visitors receive incomplete or corrupted responses (missing preloaded data). The script checks if the target is running Discourse, verifies if anonymous caching is enabled, and then attempts the attack on several endpoints (such as /categories.json, /latest.json, etc.). If successful, it verifies the impact and provides recommendations. The repository is structured simply, with the main exploit script, a README, a license, and a .gitignore. No detection-only scripts or fake payloads are present; the exploit is functional and targets a real vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.