First published: Thu Sep 29 2022(Updated: )
Discourse is an open source discussion platform. In versions prior to 2.8.9 on the `stable` branch and prior to 2.9.0.beta10 on the `beta` and `tests-passed` branches, a moderator can create new and edit existing themes by using the API when they should not be able to do so. The problem is patched in version 2.8.9 on the `stable` branch and version 2.9.0.beta10 on the `beta` and `tests-passed` branches. There are no known workarounds.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse | <2.8.9 | |
Discourse | =2.9.0-beta1 | |
Discourse | =2.9.0-beta2 | |
Discourse | =2.9.0-beta3 | |
Discourse | =2.9.0-beta4 | |
Discourse | =2.9.0-beta5 | |
Discourse | =2.9.0-beta6 | |
Discourse | =2.9.0-beta7 | |
Discourse | =2.9.0-beta8 | |
Discourse | =2.9.0-beta9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-36068 is considered a moderate severity vulnerability due to the potential for unauthorized theme modifications in Discourse.
To fix CVE-2022-36068, upgrade to Discourse version 2.8.9 or later on the stable branch or 2.9.0.beta10 or later on the beta and tests-passed branches.
CVE-2022-36068 affects Discourse versions prior to 2.8.9 and beta versions prior to 2.9.0.beta10.
CVE-2022-36068 allows unauthorized moderators to create or edit themes using the API, which can lead to unwanted changes and potential abuse.
There is no specific workaround for CVE-2022-36068; the recommended action is to update to the secure versions.