PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72727 discourse CVE debrief

CVE-2026-72727 is a stored cross-site scripting (XSS) vulnerability in the Discourse open-source discussion platform. A low-privileged user could place crafted content in the moderation review queue that executed stored XSS when a moderator viewed it on a site with a modified or disabled default Content Security Policy. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.

Vendor
discourse
Product
Unknown
CVSS
MEDIUM 4.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-10
Original CVE updated
2026-09-08
Advisory published
2026-08-10
Advisory updated
2026-09-08

Who should care

Defenders responsible for Discourse instances, particularly those with modified or disabled default Content Security Policy, should assess exposure and prioritize upgrading to a fixed version.

Why it matters

CVE-2026-72727 is a stored XSS vulnerability in Discourse that can be exploited by low-privileged users on sites with modified or disabled default Content Security Policy. Defenders should prioritize upgrading to fixed versions to prevent exploitation.

  • Potential for stored XSS execution when moderators view crafted content
  • Exposure of Discourse instances with modified or disabled default Content Security Policy
  • Need for verification of affected versions and Content Security Policy settings
  • Priority for upgrading to fixed versions to prevent exploitation

Technical summary

A low-privileged user could place crafted content in the moderation review queue that executed stored cross-site scripting when a moderator viewed it on a site with a modified or disabled default Content Security Policy. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0. Defenders should prioritize upgrading to a fixed version to prevent exploitation and review moderation review queue content for potential crafted payloads. The vulnerability can be exploited by low-privileged users on sites with modified or disabled default Content Security Policy.

Defensive priority

Defenders should prioritize upgrading to a fixed version to prevent exploitation.

Recommended defensive actions

  • Upgrade to a fixed version (2026.1.6, 2026.5.2, 2026.6.1, or 2026.7.0) to prevent exploitation
  • Review moderation review queue content for potential crafted payloads
  • Verify Content Security Policy settings on affected sites
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

A low-privileged user could place crafted content in the moderation review queue that executed stored cross-site scripting when a moderator viewed it on a site with a modified or disabled default Content Security Policy. The CVE record and NVD entry provide details on the vulnerability and fixed versions. Defenders should verify affected versions and Content Security Policy settings on affected sites. The vulnerability is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72727 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-72727

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-72727 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72727

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.