First published: Thu Feb 22 2024(Updated: )
Discourse Calendar adds the ability to create a dynamic calendar in the first post of a topic on the open-source discussion platform Discourse. Prior to version 0.4, event invitees created in topics in private categories or PMs (private messages) can be retrieved by anyone, even if they're not logged in. This problem is resolved in version 0.4 of the discourse-calendar plugin. While no known workaround is available, putting the site behind `login_required` will disallow this endpoint to be used by anonymous users, but logged in users can still get the list of invitees in the private topics.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Discourse Calendar plugin | <0.4 | |
Discourse Calendar plugin | <0.4 |
https://github.com/discourse/discourse-calendar/commit/84ef46a38cf02748ecacad16c5d9c6fec12dc8da
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-24817 has been classified as a high-severity vulnerability due to the exposure of private event invitees.
To fix CVE-2024-24817, upgrade the Discourse Calendar plugin to version 0.4 or later.
CVE-2024-24817 affects installations of the Discourse Calendar plugin prior to version 0.4.
CVE-2024-24817 allows unauthorized retrieval of event invitees created in private categories or private messages.
No, CVE-2024-24817 is not an issue if you are using version 0.4 or later of the Discourse Calendar plugin.