CVE-2025-53102 Details
Description
Discourse is an open-source community discussion platform. Prior to version 3.4.7 on the `stable` branch and version 3.5.0.beta.8 on the `tests-passed` branch, upon issuing a physical security key for 2FA, the server generates a WebAuthn challenge, which the client signs. The challenge is not cleared from the user’s session after authentication, potentially allowing reuse and increasing security risk. This is fixed in versions 3.4.7 and 3.5.0.beta.8.
A vulnerability exists in Discourse, an open-source community discussion platform, in versions prior to 3.4.7 on the stable branch and prior to 3.5.0.beta.8 on the tests-passed branch. The issue arises when a physical security key is used for two-factor authentication (2FA). The server generates a WebAuthn challenge that the client signs, but this challenge is not removed from the user's session after authentication. This oversight could allow the challenge to be reused, posing a security risk.
Users can update to Discourse versions 3.4.7 or later on the stable branch, or 3.5.0.beta.8 or later on the tests-passed branch.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 29, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-384 | Session Fixation | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| discourse discourse | < 3.4.6 <= 3.5.0 3.5.0 beta1 3.5.0 beta2 3.5.0 beta3 3.5.0 beta4 3.5.0 beta5 3.5.0 beta6 3.5.0 beta7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 25, 2025 | Initial Analysis | [email protected] |
| Jul 29, 2025 | New CVE Received | [email protected] |