First published: Wed Jul 03 2024(Updated: )
Discourse is an open-source discussion platform. Prior to version 3.2.3 on the `stable` branch, version 3.3.0.beta3 on the `beta` branch, and version 3.3.0.beta4-dev on the `tests-passed` branch, a rogue staff user could suspend other staff users preventing them from logging in to the site. The issue is patched in version 3.2.3 on the `stable` branch, version 3.3.0.beta3 on the `beta` branch, and version 3.3.0.beta4-dev on the `tests-passed` branch. No known workarounds are available.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse | <3.2.3 | |
Discourse | <3.3.0 | |
Discourse | =3.3.0-beta1 | |
Discourse | =3.3.0-beta2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-36113 is considered to be a high severity vulnerability due to its potential to disrupt user access and management within Discourse.
To fix CVE-2024-36113, upgrade your Discourse installation to version 3.2.3 or higher on the stable branch, 3.3.0.beta3 or higher on the beta branch, or 3.3.0.beta4-dev on the tests-passed branch.
CVE-2024-36113 affects Discourse installations prior to version 3.2.3 on stable, 3.3.0.beta3 on beta, and specific beta versions.
The impact of CVE-2024-36113 is that a malicious staff user can suspend other staff users, potentially leading to unauthorized access control and operational disruptions.
CVE-2024-36113 was reported and became publicly known in 2024.