User can see invitees in events created in PMs and private categories
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-200.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA discourse-calendar (discourse) Fixed in 0.4
Timeline
- 2026-10-02 Threatist record created from CVE-2024-24817
References
More discourse Calendar vulnerabilities
- TI-2024-17235 Uninvited user is able to join and mark the attendance of the the private event CVSS 3.1MEDIUM 6.5
- TI-2024-30374 Discourse Calendar plugin event names susceptible to XSS CVSS 3.1MEDIUM 6.1
- TI-2022-20254 Discourse-calendar exposes members of hidden groups CVSS 3.1MEDIUM 5.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences