{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45303 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45303 is a medium-severity cross-site scripting vulnerability in discourse-calendar, published on 12 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-45303 and fix it if it is affected.\n\nWhat it is: CVE-2024-45303 is a medium-severity cross-site scripting vulnerability in discourse-calendar, published on 12 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-45303 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-45303/ (Markdown: https://insights.sbomify.com/CVE-2024-45303/index.md)","id":"CVE-2024-45303","markdown":"https://insights.sbomify.com/CVE-2024-45303/index.md","name":"CVE-2024-45303","record":{"aliases":["GHSA-rq37-8pf3-4xc8"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Discourse Calendar plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via event names in Discourse Calendar, requiring disabled CSP, leading to potential account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"calendar","vendor":"discourse"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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 Discourse’s default Content Security Policy. The issue is patched in version 0.5 of the Discourse Calendar plugin.","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":"Discourse Calendar plugin event names susceptible to XSS","id":"CVE-2024-45303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Business logic in cairo-contracts","id":"CVE-2024-45304"},"packages":[],"prev":{"headline":"CRLF Injection in RestSharp's `RestRequest.AddHeader` method","id":"CVE-2024-45302"},"products":["discourse-calendar"],"published":"2024-09-12","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":4.3,"headline":"User can see invitees in events created in PMs and private categories","id":"CVE-2024-24817","kev_date_added":null,"published":"2024-02-22"},{"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-09-12","vendors":["discourse"]},"summary":"Attackers can inject malicious scripts via event names in Discourse Calendar, requiring disabled CSP, leading to potential account takeover.","url":"https://insights.sbomify.com/CVE-2024-45303/"}