{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-26145 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-26145 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-26145 is a medium-severity missing authorization vulnerability in discourse-calendar, published on 21 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-26145 and fix it if it is affected.\n\nWhat it is: CVE-2024-26145 is a medium-severity missing authorization vulnerability in discourse-calendar, published on 21 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-26145 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-26145/ (Markdown: https://insights.sbomify.com/CVE-2024-26145/index.md)","id":"CVE-2024-26145","markdown":"https://insights.sbomify.com/CVE-2024-26145/index.md","name":"CVE-2024-26145","record":{"aliases":["GHSA-4hh7-6m34-p2jp"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse Calendar plugin","requires_auth":"low_privilege","summary":"Uninvited users can join and mark attendance for private events in Discourse Calendar by crafting specific requests, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"calendar","vendor":"discourse"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Discourse Calendar adds the ability to create a dynamic calendar in the first post of a topic on Discourse. Uninvited users are able to gain access to private events by crafting a request to update their attendance. This problem is resolved in commit dfc4fa15f340189f177a1d1ab2cc94ffed3c1190. As a workaround, one may use post visibility to limit access.","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":"Uninvited user is able to join and mark the attendance of the the private event","id":"CVE-2024-26145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Possible Denial of Service Vulnerability in Rack Header Parsing","id":"CVE-2024-26146"},"packages":[],"prev":{"headline":"Possible Sensitive Session Information Leak in Active Storage","id":"CVE-2024-26144"},"products":["discourse-calendar"],"published":"2024-02-21","related":[{"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":"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":"total"},"state":"PUBLISHED","updated":"2024-08-27","vendors":["discourse"]},"summary":"Uninvited users can join and mark attendance for private events in Discourse Calendar by crafting specific requests, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2024-26145/"}