CVE-2024-24817
4.3 · MEDIUMOverview
CVE-2024-24817 is a medium-severity vulnerability affecting discourse calendar. It was published on February 22, 2024 and has a CVSS 3.1 base score of 4.3 (MEDIUM).
This vulnerability has a CVSS 3.1 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
Technical Description
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.
Remediation
Check the references section for vendor advisories and patches from discourse. Update calendar to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| discourse | calendar | >= 0, < 0.4 | Affected |
References
Frequently Asked Questions
What is CVE-2024-24817?
CVE-2024-24817 is a medium-severity vulnerability affecting discourse calendar. It was published on February 22, 2024 and has a CVSS 3.1 base score of 4.3 (MEDIUM).
How severe is CVE-2024-24817?
This vulnerability has a CVSS 3.1 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2024-24817?
Check the references section for vendor advisories and patches from discourse. Update calendar to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2024-24817?
CyberStrike's AI-powered security agents can automatically detect CVE-2024-24817 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2024
View all →OCSInventory allow stored email template with special characters that lead to a Stored cross-site Sc
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation