CVE-2024-24817: User can see invitees in events created in PMs and private categories
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 loginrequired 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
discourse-calendarto a version that resolves this vulnerability.Fixed in 0.4 - Configuration
Put the Discourse site behind `login_required` so the invitees endpoint in PMs/private categories cannot be used by anonymous users; logged-in users can still view invitees.
Discourse login_required = true
Event History
Frequently Asked Questions
What is the severity of CVE-2024-24817?
CVE-2024-24817 has been classified as a high-severity vulnerability due to the exposure of private event invitees.
How do I fix CVE-2024-24817?
To fix CVE-2024-24817, upgrade the Discourse Calendar plugin to version 0.4 or later.
What types of Discourse Calendar installations are affected by CVE-2024-24817?
CVE-2024-24817 affects installations of the Discourse Calendar plugin prior to version 0.4.
What data is exposed in CVE-2024-24817?
CVE-2024-24817 allows unauthorized retrieval of event invitees created in private categories or private messages.
Is CVE-2024-24817 still an issue if I use version 0.4 or later?
No, CVE-2024-24817 is not an issue if you are using version 0.4 or later of the Discourse Calendar plugin.