{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-24817 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-24817 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-24817 is a medium-severity vulnerability in discourse-calendar, published on 22 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-24817 and fix it if it is affected.\n\nWhat it is: CVE-2024-24817 is a medium-severity vulnerability in discourse-calendar, published on 22 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-24817 in the wild and no public exploit code.\n\nAffected product: discourse-calendar. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-24817/ (Markdown: https://insights.sbomify.com/CVE-2024-24817/index.md)","id":"CVE-2024-24817","markdown":"https://insights.sbomify.com/CVE-2024-24817/index.md","name":"CVE-2024-24817","record":{"aliases":["GHSA-wwq5-g5cp-c69f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse calendar plugin","requires_auth":"low_privilege","summary":"Unauthenticated attackers can view invitee lists for events in private Discourse categories or PMs, exposing user participation data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"calendar","vendor":"discourse"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"User can see invitees in events created in PMs and private categories","id":"CVE-2024-24817","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"EspoCRM weakness in \"Forgot password\"","id":"CVE-2024-24818"},"packages":[],"prev":{"headline":"Cross-site scripting (XSS) vulnerability in samples with enabled the preview feature","id":"CVE-2024-24816"},"products":["discourse-calendar"],"published":"2024-02-22","related":[{"cvss_score":6.5,"headline":"Uninvited user is able to join and mark the attendance of the the private event","id":"CVE-2024-26145","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":6.1,"headline":"Discourse Calendar plugin event names susceptible to XSS","id":"CVE-2024-45303","kev_date_added":null,"published":"2024-09-12"},{"cvss_score":4.3,"headline":"Discourse-calendar exposes members of hidden groups","id":"CVE-2022-41913","kev_date_added":null,"published":"2022-11-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-21","vendors":["discourse"]},"summary":"Unauthenticated attackers can view invitee lists for events in private Discourse categories or PMs, exposing user participation data.","url":"https://insights.sbomify.com/CVE-2024-24817/"}