CVE-2026-53963 json
Discourse: Stored-XSS in 2FA delete confirmation modal
published 4mo ago modified 2mo ago also BIT-discourse-2026-53963 , EUVD-2026-42738 , GHSA-wg5x-7f23-m3r5
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami discourse 2026.1.5, 2026.4.2, 2026.5.1
- discourse discourse 2026.1.5, 2026.4.2, 2026.5.1
- github.com/discourse/discourse@40de62c commit
- github.com/discourse/discourse@529e17d commit
- github.com/discourse/discourse@d92973e commit
- github.com/discourse/discourse@daea521 commit
- github.com/discourse/discourse/releases/tag/v2026.1.5 release
- github.com/discourse/discourse/releases/tag/v2026.4.2 release
- github.com/discourse/discourse/releases/tag/v2026.5.1 release
- github.com/discourse/discourse/releases/tag/v2026.6.0 release
Is CVE-2026-53963 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H |
| OSV | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | discourse | >=2026.1.0, <2026.1.5 >=2026.4.0, <2026.4.2 >=2026.5.0, <2026.5.1 |
2026.1.5 2026.4.2 2026.5.1 |
Affected products
- discourse discourse
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/discourse/discourse/commit/40de62cddadc65c328a1028ab999f3fa94adbfed
patch
-
github.com
/discourse/discourse/commit/529e17d4d570a48972e7cf64720e5dd1fdf23ca8
patch
-
github.com
/discourse/discourse/commit/d92973e51a46cf6dd20c71e6068e6769b67eea5b
patch
-
github.com
/discourse/discourse/commit/daea5214d833eacbdd3b1a78d99eb14e9cabd915
patch
-
github.com
/discourse/discourse/security/advisories/GHSA-wg5x-7f23-m3r5
mitigation, vendor-advisory, advisory
-
github.com
/discourse/discourse/releases/tag/v2026.1.5
release-notes, article
-
github.com
/discourse/discourse/releases/tag/v2026.4.2
release-notes, article
-
github.com
/discourse/discourse/releases/tag/v2026.5.1
release-notes, article
-
github.com
/discourse/discourse/releases/tag/v2026.6.0
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-53963
web
Sources
- CVE List CVE-2026-53963
- NVD CVE-2026-53963
- OSV BIT-discourse-2026-53963
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.