Loading vulnerability…
CVE-2023-45131 affects Discourse, an open source community discussion platform. The vulnerability allows new chat messages to be read by sending an unauthenticated POST request to MessageBus. In effect, access control was not properly enforced for chat message retrieval via the MessageBus interface, enabling unauthorized parties to obtain chat content without authentication. The issue is fixed in Discourse 3.1.1 stable and 3.2.0.beta2.
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.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Ruby exploit script (CVE-2023-45131.rb) targeting Discourse installations vulnerable to CVE-2023-45131. The exploit leverages unauthenticated access to the MessageBus endpoints in Discourse to enumerate chat channels, access private chat messages, monitor real-time chat activity, and enumerate users. The script performs a series of tests against the target Discourse instance, attempting to access and parse data from endpoints such as /message-bus/poll, /message-bus/subscribe, /message-bus/diagnostics, and /message-bus/long-poll, as well as chat-specific endpoints like /chat/new-messages, /chat/channel-status, and /chat/user-tracking. The exploit is operational and provides actionable results, including a report of discovered vulnerabilities and remediation advice. The repository is structured simply, with the main exploit script, a license, a .gitignore, and a minimal README.
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.
5 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.