CVE-2023-43659
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. Improper escaping of user input allowed for Cross-site Scripting attacks via the digest email preview UI. This issue only affects sites with CSP disabled. This issue has been patched in the 3.1.1 stable release as well as the 3.2.0.beta1 release. Users are advised to upgrade. Users unable to upgrade should ensure CSP is enabled on the forum.
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 confidenceCross-site scripting (XSS) vulnerability in Discourse's digest email preview UI due to improper escaping of user input. The vulnerability is exploitable when Content Security Policy (CSP) is disabled, allowing attackers to inject malicious scripts via the preview feature that execute 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.1.1= 3.2.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 installed Discourse versionLog into the Discourse admin panel and navigate to /about, or check the git version by running `git describe --tags` in the Discourse installation directoryAffected if The version is 3.1.1 or earlier, or exactly 3.2.0
-
Verify Content Security Policy statusAccess the Discourse admin panel, go to the Security settings, and check if Content Security Policy headers are enabled. Alternatively, inspect HTTP response headers for the presence of Content-Security-Policy headers when loading the forumAffected if CSP headers are disabled or not present in HTTP responses
-
Confirm digest email preview accessibilityNavigate to the digest email preview endpoint (typically /admin/email/digest-preview or similar path in the admin interface) to verify the feature is accessibleAffected if The digest preview interface loads without errors and accepts user input in preview fields
You are affected if your installed Discourse version is 3.1.1 or earlier, or exactly 3.2.0, AND Content Security Policy headers are disabled in your environment.
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 · scopedUpgrade Discourse to version 3.1.1 (stable) or 3.2.0.beta1 or later, or enable Content Security Policy (CSP) headers on the forum as an alternative workaround.
Discourse 3.1.1 stable (or 3.2.0.beta1 and above)
- Upgrade Discourse to version 3.1.1 stable or later (or 3.2.0.beta1 and above) to receive the security patch
- After upgrading, verify the digest email preview functionality works correctly
- Alternatively, if upgrade is not immediately possible, ensure Content Security Policy (CSP) is enabled on the Discourse forum to mitigate this vulnerability
- To enable CSP, go to Discourse admin settings and enable the 'content_security_policy' setting
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43659 — 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-2023-43659 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