Quick answers
- Is CVE-2026-72727 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72727 being exploited in the wild.
- How severe is CVE-2026-72727?
- Informational severity, with a CVSS score of 4.8, published 10 August 2026.
- Which products and versions are affected?
- Discourse prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.
- Is there a fix for CVE-2026-72727?
- A patch was published on 2026-07-28. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72727 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-72727?
- Check whether you run Discourse at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a stored cross-site scripting (XSS) vulnerability in Discourse's moderation review queue. A low-privileged user can craft and submit content containing JavaScript that persists in the moderation queue. When a moderator later views the queued content, the JavaScript executes in the moderator's browser session. The vulnerability is contingent on the site having modified or disabled Discourse's default Content Security Policy (CSP), which normally prevents inline script execution. The attack requires the attacker to have user account privileges and the moderator to view the crafted content. Patches are available in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.
Affected products
- Discourse Discourse prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0
Timeline
- 2026-07-28: disclosed
- 2026-07-28: patched