First published: Tue Jan 30 2024(Updated: )
Discourse is an open-source discussion platform. Improperly sanitized user input could lead to an XSS vulnerability in some situations. This vulnerability only affects Discourse instances which have disabled the default Content Security Policy. The vulnerability is patched in 3.1.5 and 3.2.0.beta5. As a workaround, ensure Content Security Policy is enabled and does not include `unsafe-inline`.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse | <3.1.5 | |
Discourse | <3.2.0 | |
Discourse | =3.2.0-beta1 | |
Discourse | =3.2.0-beta2 | |
Discourse | =3.2.0-beta3 | |
Discourse | =3.2.0-beta4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-23834 is classified as a medium severity vulnerability due to its potential for XSS attacks.
To fix CVE-2024-23834, update your Discourse instance to version 3.1.5 or later, or ensure that your Content Security Policy is enabled.
CVE-2024-23834 affects Discourse instances that have disabled the default Content Security Policy.
CVE-2024-23834 is an XSS vulnerability caused by improperly sanitized user input.
Discourse versions before 3.1.5, including specific beta versions up to 3.2.0, are vulnerable to CVE-2024-23834.