LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27154: Discourse has XSS when editing a malicious post

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, a user full name can be evaluated as raw HTML when the following settings are set: `display_name_on_posts` => true; and `prioritize_username_in_ux` => false. Editing a post of a malicious user would trigger an XSS. Versions 2025.12.2, 2026.1.1, and 2026.2.0 patch the issue. No known workarounds are available.

LowCVSS 1.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Discourse sites with specific display-name settings could expose staff or users editing a malicious user’s post to cross-site scripting. The issue is rated low, but it can affect trust in forum administration workflows. Fixed versions are available; no workaround is listed by the vendor advisory.

Executive priority

Treat as a routine but necessary forum-platform update. The business risk is low, but patching reduces the chance of script execution during content moderation or editing workflows. Prioritize exposed public communities using the affected settings.

Technical view

CVE-2026-27154 is a CWE-79 XSS in Discourse. Before 2025.12.2, 2026.1.1, and 2026.2.0, a user full name may be evaluated as raw HTML when display_name_on_posts is true and prioritize_username_in_ux is false. Editing a malicious user’s post triggers the XSS condition.

Likely exposure

Exposure is limited to Discourse instances running affected versions with both vulnerable settings enabled. The triggering scenario involves editing a post from a malicious user. Sites not using those settings, or already updated to the listed fixed versions, are less likely to be exposed.

Exploitation context

The CVE record is not listed in KEV, and the provided sources do not report active exploitation. The advisory describes a low-severity XSS requiring a malicious user profile name and the vulnerable display-name configuration.

Researcher notes

Evidence is limited to the CVE record and GitHub advisory. The affected condition is configuration-dependent. Do not assume broad impact across all Discourse deployments. The source bundle states no known workarounds and identifies fixed versions only.

Mitigation direction

  • Upgrade Discourse to 2025.12.2, 2026.1.1, 2026.2.0, or later as applicable.
  • Check Discourse’s security advisory for branch-specific upgrade guidance.
  • No vendor workaround is listed; prioritize patching over configuration-only assumptions.

Validation and detection

  • Inventory Discourse instances and record their release branch and version.
  • Verify whether display_name_on_posts is true and prioritize_username_in_ux is false.
  • Confirm upgraded instances are at or above the fixed versions.
  • Review recent malicious or suspicious user full names if vulnerable settings were enabled.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27154 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
1.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
1.3CVSS 4.0LowCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

1.3Low
CVSS 4.0 vector shape for CVE-2026-27154Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
discoursediscourse< 2025.12.2, >= 2026.1.0-latest, < 2026.1.1, >= 2026.2.0-latest, < 2026.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.