First published: Thu Mar 24 2022(Updated: )
Discourse is an open source discussion platform. Versions 2.8.2 and prior in the `stable` branch, 2.9.0.beta3 and prior in the `beta` branch, and 2.9.0.beta3 and prior in the `tests-passed` branch are vulnerable to a data leak. Users can request an export of their own activity. Sometimes, due to category settings, they may have category membership for a secure category. The name of this secure category is shown to the user in the export. The same thing occurs when the user's post has been moved to a secure category. A patch for this issue is available in the `main` branch of Discourse's GitHub repository and is anticipated to be part of future releases.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse | <=2.8.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-24782 is classified as a moderate severity vulnerability due to the potential for data leakage.
To mitigate CVE-2022-24782, upgrade to Discourse version 2.8.3 or later for the stable branch, or 2.9.0.beta4 or later for the beta branch.
CVE-2022-24782 affects Discourse versions 2.8.2 and prior in the stable branch, and 2.9.0.beta3 and prior in both beta and tests-passed branches.
CVE-2022-24782 is a data leak vulnerability that allows users to export potentially sensitive activity data.
Users of Discourse versions that are 2.8.2 or older, as well as those using any 2.9.0 beta versions, are potentially impacted by CVE-2022-24782.