{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0855 exists.","fix":"No fix has been published for CVE-2024-0855 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0855 is a medium-severity missing authorization vulnerability in Unknown Spiffy Calendar, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-0855 and fix it if it is affected.\n\nWhat it is: CVE-2024-0855 is a medium-severity missing authorization vulnerability in Unknown Spiffy Calendar, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0855 exists.\n\nAffected product: Unknown Spiffy 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-0855/ (Markdown: https://insights.sbomify.com/CVE-2024-0855/index.md)","id":"CVE-2024-0855","markdown":"https://insights.sbomify.com/CVE-2024-0855/index.md","name":"CVE-2024-0855","record":{"aliases":["GHSA-g77v-mcj9-92j3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can spoof event authorship by manipulating parameters, deceiving admins and users about content ownership in Spiffy Calendar.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"spiffy_calendar","vendor":"spiffyplugins"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"The Spiffy Calendar WordPress plugin before 4.9.9 doesn't check the event_author parameter, and allows any user to alter it when creating an event, leading to deceiving users/admins that a page was created by a Contributor+.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Spiffy Calendar \u003c 4.9.9 - Broken Access Control","id":"CVE-2024-0855","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Booking Calendar \u003c 1.3.83 - CSRF appointment scheduling","id":"CVE-2024-0856"},"packages":[],"prev":{"headline":"Open redirect in DiskStation Manager (DSM)","id":"CVE-2024-0854"},"products":["Spiffy Calendar"],"published":"2024-02-27","related":[{"cvss_score":8.5,"headline":"WordPress Spiffy Calendar Plugin \u003c= 4.9.1 is vulnerable to SQL Injection","id":"CVE-2022-46859","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":7.6,"headline":"WordPress spiffy-calendar plugin \u003c= 4.9.11 - SQL Injection vulnerability","id":"CVE-2024-38692","kev_date_added":null,"published":"2024-07-22"},{"cvss_score":7.1,"headline":"WordPress Spiffy Calendar plugin \u003c= 4.9.13 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-45458","kev_date_added":null,"published":"2024-09-15"},{"cvss_score":6.5,"headline":"WordPress Spiffy Calendar plugin \u003c= 4.9.13 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-45457","kev_date_added":null,"published":"2024-09-15"},{"cvss_score":6.5,"headline":"WordPress Spiffy Calendar Plugin \u003c= 4.9.5 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-49745","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":6.3,"headline":"WordPress Spiffy Calendar plugin \u003c= 4.9.0 - Edit/Delete event via IDOR vulnerability","id":"CVE-2022-29434","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":5.8,"headline":"WordPress Spiffy Calendar Plugin \u003c= 4.9.3 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-32122","kev_date_added":null,"published":"2023-08-18"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-08","vendors":["Unknown"]},"summary":"Attackers can spoof event authorship by manipulating parameters, deceiving admins and users about content ownership in Spiffy Calendar.","url":"https://insights.sbomify.com/CVE-2024-0855/"}