{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37919 exists.","fix":"No fix has been published for CVE-2023-37919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-37919 is a medium-severity vulnerability in calcom cal.com, published on 25 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-37919 and fix it if it is affected.\n\nWhat it is: CVE-2023-37919 is a medium-severity vulnerability in calcom cal.com, published on 25 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37919 exists.\n\nAffected product: calcom cal.com. 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-2023-37919/ (Markdown: https://insights.sbomify.com/CVE-2023-37919/index.md)","id":"CVE-2023-37919","markdown":"https://insights.sbomify.com/CVE-2023-37919/index.md","name":"CVE-2023-37919","record":{"aliases":["GHSA-cpf2-q635-xrwx"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Cal.com scheduling software","requires_auth":"low_privilege","summary":"Attackers can maintain unauthorized access to Cal.com accounts after 2FA is enabled because existing sessions are not invalidated.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cal.com","vendor":"cal"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Cal.com is open-source scheduling software. A vulnerability allows active sessions associated with an account to remain active even after enabling 2FA. When activating 2FA on a Cal.com account that is logged in on two or more devices, the account stays logged in on the other device(s) stays logged in without having to verify the account owner's identity. As of time of publication, no known patches or workarounds exist.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cal.com not expiring old sessions after enabling 2FA","id":"CVE-2023-37919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Certifi's removal of e-Tugra root certificate","id":"CVE-2023-37920"},"packages":[],"prev":{"headline":"API token authentication bypass in HTTP endpoints in Dapr","id":"CVE-2023-37918"},"products":["cal.com"],"published":"2023-07-25","related":[{"cvss_score":10,"headline":"Cal.com has an Authentication Bypass via Unvalidated Email in Custom JWT Callback","id":"CVE-2026-23478","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":9.9,"headline":"Cal.com Authentication Bypass via bad TOTP + password checks","id":"CVE-2025-66489","kev_date_added":null,"published":"2025-12-03"},{"cvss_score":8.8,"headline":"Improper Access Control in calcom/cal.com","id":"CVE-2023-1647","kev_date_added":null,"published":"2023-03-27"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-16","vendors":["calcom"]},"summary":"Attackers can maintain unauthorized access to Cal.com accounts after 2FA is enabled because existing sessions are not invalidated.","url":"https://insights.sbomify.com/CVE-2023-37919/"}