CVE-2026-32607: Discourse: Stored XSS via unescaped assignee name

Published Mar 31, 2026
·
Updated

Discourse is an open-source discussion platform. From versions 2026.1.0-latest to before 2026.1.3, 2026.2.0-latest to before 2026.2.2, and 2026.3.0-latest to before 2026.3.0, when the hidden prioritizefullnameinux site setting is enabled (defaults to false, requires console access to change), user and group display names are rendered without HTML escaping in several assignment-related UI paths. This allows users with assign permission to inject arbitrary HTML/JavaScript that executes in the browser of any user viewing an affected topic. This issue has been patched in versions 2026.1.3, 2026.2.2, and 2026.3.0.

Affected Software

5 affected components
Discourse Discourse>=2026.1.0<2026.1.3, >=2026.2.0<2026.2.2, <2026.3.0
Discourse Discourse>=2026.1.0<2026.1.3
Discourse Discourse>=2026.2.0<2026.2.2
Discourse Discourse=2026.3.0
Discourse Discourse=2026.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.1.3
  2. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.2.2
  3. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.3.0

Event History

Mar 31, 2026
CVE Published
via MITRE·05:40 PM
Data Sourced
via MITRE·05:40 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-32607?

CVE-2026-32607 is categorized as a stored XSS vulnerability that can potentially allow attackers to execute arbitrary scripts in the context of a user's session.

2

How do I fix CVE-2026-32607?

To fix CVE-2026-32607, update Discourse to version 2026.1.3, 2026.2.2, or later if you are using affected versions.

3

Which versions of Discourse are affected by CVE-2026-32607?

CVE-2026-32607 affects Discourse versions 2026.1.0 to 2026.1.2, 2026.2.0 to 2026.2.1, and all versions before 2026.3.0.

4

What does the hidden prioritize_full_name_in_ux setting do in relation to CVE-2026-32607?

When the hidden prioritize_full_name_in_ux site setting is enabled, it may expose the stored XSS vulnerability in specific contexts.

5

What kind of attacks can be performed due to CVE-2026-32607?

CVE-2026-32607 could enable attackers to execute malicious scripts, potentially stealing cookies, session tokens, or sensitive information from users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203