{"answers":{"affected":"2 open source packages ship an affected version, including joedolson/my-calendar.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40308 exists.","fix":"Upgrade joedolson/my-calendar to 3.7.7 or later.","what":"CVE-2026-40308 is a high-severity vulnerability in joedolson my-calendar, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40308 and fix it if it is affected.\n\nWhat it is: CVE-2026-40308 is a high-severity vulnerability in joedolson my-calendar, published on 16 Apr 2026. 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-2026-40308 exists.\n\nAffected packages and fixed versions:\n- joedolson/my-calendar (Packagist): affected all versions; fixed in 3.7.7\n- joedolson/my-calendar (Packagist): affected all versions; fixed in 3.7.7\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-2026-40308/ (Markdown: https://insights.sbomify.com/CVE-2026-40308/index.md)","id":"CVE-2026-40308","markdown":"https://insights.sbomify.com/CVE-2026-40308/index.md","name":"CVE-2026-40308","record":{"aliases":["GHSA-2mvx-f5qm-v2ch"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract private calendar events from any sub-site on WordPress Multisite installations or cause denial of service on single-site installations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"My Calendar is a WordPress plugin for managing calendar events. In versions 3.7.6 and below, the mc_ajax_mcjs_action AJAX endpoint, registered for unauthenticated users, passes user-supplied arguments through parse_str() without validation, allowing injection of arbitrary parameters including a site value. On WordPress Multisite installations, this enables an unauthenticated attacker to call switch_to_blog() with an arbitrary site ID and extract calendar events from any sub-site on the network, including private or hidden events. On standard Single Site installations, switch_to_blog() does not exist, causing an uncaught PHP fatal error and crashing the worker thread, creating an unauthenticated denial of service vector. This issue has been fixed in version 3.7.7.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-40308.yaml","stars":null,"title":"My Calendar WordPress Plugin - Information Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"My Calendar: Unauthenticated Information Disclosure (IDOR) via Multisite switch_to_blog","id":"CVE-2026-40308","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Masa CMS CSRF in trash management allows unauthorized permanent deletion of deleted content","id":"CVE-2026-40309"},"packages":[{"ecosystem":"Packagist","fixed":["3.7.7"],"introduced":["0"],"last_affected":[],"package":"joedolson/my-calendar","purl":null,"source":"GHSA-2mvx-f5qm-v2ch"},{"ecosystem":"Packagist","fixed":["3.7.7"],"introduced":["0"],"last_affected":[],"package":"joedolson/my-calendar","purl":"pkg:composer/joedolson/my-calendar","source":"GHSA-2mvx-f5qm-v2ch"}],"prev":{"headline":"DNN has same HostGUID for all new installs","id":"CVE-2026-40306"},"products":["my-calendar"],"published":"2026-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-17","vendors":["joedolson"]},"summary":"Unauthenticated attackers can extract private calendar events from any sub-site on WordPress Multisite installations or cause denial of service on single-site installations.","url":"https://insights.sbomify.com/CVE-2026-40308/"}