CVE-2024-47772
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDiscourse is an open source platform for community discussion. An attacker can execute arbitrary JavaScript on users' browsers by sending a maliciously crafted chat message and replying to it. This issue only affects sites with CSP disabled. This problem is patched in the latest version of Discourse. All users are advised to upgrade. Users unable to upgrade should ensure CSP is enabled on the forum. Users who do upgrade should also consider enabling a CSP as well as a proactive measure.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored XSS vulnerability exists in Discourse's chat feature where an attacker can execute arbitrary JavaScript by sending a maliciously crafted chat message and replying to it, allowing execution in users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.3.2< 3.4.0= 3.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Discourse versionAccess the Discourse admin panel at /admin/dashboard, or check the version via the API at /admin/api/version, or run `git log` in the Discourse installation directoryAffected if The installed version is less than 3.3.2, or is 3.4.0, or is less than 3.4.0 (meaning versions 3.3.0 through 3.3.1, and 3.4.0 are affected; 3.3.2 and 3.4.1+ are fixed)
-
Verify chat feature is enabledNavigate to Discourse admin panel, go to Plugins or Chat settings, and check whether the chat feature is turned onAffected if The chat feature is currently enabled in the Discourse settings
-
Inspect chat messages for suspicious contentIn the Discourse admin panel, review recent chat messages or query the database chat_message_records table for HTML script tags, javascript: URIs, or event handler attributesAffected if Chat messages contain malicious script tags, inline JavaScript, or suspicious event handlers that could indicate exploitation
You are affected if your Discourse version is vulnerable (less than 3.3.2, or 3.4.0) AND the chat feature is enabled, as the XSS only triggers in the chat component.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.3.23.4.0
Upgrade to the latest Discourse version or enable Content Security Policy (CSP) on the forum to prevent the XSS execution.
Latest stable Discourse release (> 3.4.0, for example 3.5.0 or higher)
- Backup your Discourse installation and database before upgrading
- Upgrade Discourse to the latest stable version (greater than 3.4.0)
- After upgrading, verify the chat functionality works correctly
- As a proactive security measure, enable Content Security Policy (CSP) in your Discourse settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47772 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data