CVE-2026-53963 — Discourse: Stored-XSS in 2FA delete confirmation modal
Discourse is an open-source discussion platform. Prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5, a malicious second factor name on an attacker-controlled account was not escaped in the delete confirmation dialog, allowing stored cross-site scripting when an administrator impersonated that account. This issue is fixed in versions 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented mitigation — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Discourse Discourse).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Discourse | Discourse | ≥ 2026.1.0 and < 2026.1.5≥ 2026.4.0 and < 2026.4.2≥ 2026.5.0 and < 2026.5.1version 2026.6.0 | Vulnerable | NIST National Vulnerability Database |
| Discourse | Discourse | version >= 2026.1.0-latest, < 2026.1.5version >= 2026.4.0-latest, < 2026.4.2version >= 2026.5.0-latest, < 2026.5.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.0 | CVSS 3.1 | Critical | 2.3 | 6.0 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.3 | CVSS 3.1 | High | 2.1 | 5.2 | security-advisories@github.com via NIST National Vulnerability Database |
| 7.3 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · discourse/discourse
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 9.0
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- github.com/discourse/discourse/security/advisories/GHSA-wg5x-7f23-m3r5
- github.com/discourse/discourse/commit/daea5214d833eacbdd3b1a78d99eb14e9cabd915
- github.com/discourse/discourse/commit/40de62cddadc65c328a1028ab999f3fa94adbfed
- github.com/discourse/discourse/commit/d92973e51a46cf6dd20c71e6068e6769b67eea5b
- github.com/discourse/discourse/commit/529e17d4d570a48972e7cf64720e5dd1fdf23ca8
- github.com/discourse/discourse/releases/tag/v2026.6.0
- github.com/discourse/discourse/releases/tag/v2026.5.1
- github.com/discourse/discourse/releases/tag/v2026.4.2
- github.com/discourse/discourse/releases/tag/v2026.1.5
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-91159 Discourse: Stored oEmbed HTML injection via allowed iframe 1d
- High CVE-2026-91157 Discourse: Media uploads remain publicly accessible after category permissions are restricted 1d
- High CVE-2026-91156 Discourse: Chat MessageBus delivers read-restricted messages to unauthorized users 1d
- Medium CVE-2026-59828 Discourse: Hidden post revisions leak through adjacent visible diffs Jul 9, 2026
- Medium CVE-2026-55424 Discourse: Topic featured link susceptible to stored XSS Jul 9, 2026
- High CVE-2026-49256 Discourse: Hidden tag names leaked via category serializers Jul 9, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-53963 is "Discourse: Stored-XSS in 2FA delete confirmation modal", rated Critical. It affects Discourse (Discourse); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.0 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.