Discourse Calendar
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Discourse Calendar.
By the Year
In 2024 there have been 1 vulnerability in Discourse Calendar with an average score of 6.1 out of ten. Calendar did not have any published security vulnerabilities last year. That is, 1 more vulnerability have already been reported in 2024 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 1 | 6.10 |
| 2023 | 0 | 0.00 |
| 2022 | 1 | 5.40 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Calendar vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Discourse Calendar Security Vulnerabilities
Discourse Calendar plugin adds the ability to create a dynamic calendar in the first post of a topic to Discourse
CVE-2024-45303
6.1 - Medium
- September 12, 2024
Discourse Calendar plugin adds the ability to create a dynamic calendar in the first post of a topic to Discourse. Rendering event names can be susceptible to XSS attacks. This vulnerability only affects sites which have modified or disabled Discourses default Content Security Policy. The issue is patched in version 0.5 of the Discourse Calendar plugin.
XSS
Discourse-calendar is a plugin for the Discourse messaging platform
CVE-2022-41913
5.4 - Medium
- November 14, 2022
Discourse-calendar is a plugin for the Discourse messaging platform which adds the ability to create a dynamic calendar in the first post of a topic. Members of private groups or public groups with private members can be listed by users, who can create and edit post events. This vulnerability only affects sites which have discourse post events enabled. This issue has been patched in commit `ca5ae3e7e` which will be included in future releases. Users unable to upgrade should disable the `discourse_post_event_enabled` setting to fully mitigate the issue. Also, it's possible to prevent regular users from using this vulnerability by removing all groups from the `discourse_post_event_allowed_on_groups` but note that moderators will still be able to use it.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Discourse Calendar or by Discourse? Click the Watch button to subscribe.
