{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22113 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22113 is a high-severity authentication bypass vulnerability in Bottelet DaybydayCRM, published on 13 Jan 2022. 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-2022-22113 and fix it if it is affected.\n\nWhat it is: CVE-2022-22113 is a high-severity authentication bypass vulnerability in Bottelet DaybydayCRM, published on 13 Jan 2022. 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-2022-22113 in the wild and no public exploit code.\n\nAffected product: Bottelet DaybydayCRM. 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-2022-22113/ (Markdown: https://insights.sbomify.com/CVE-2022-22113/index.md)","id":"CVE-2022-22113","markdown":"https://insights.sbomify.com/CVE-2022-22113/index.md","name":"CVE-2022-22113","record":{"aliases":["GHSA-rjr7-pjq2-v9j9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"DayByDay CRM","requires_auth":"none","summary":"Attackers can maintain access to DayByDay CRM after a password change because existing sessions are not invalidated.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Mend","cpe":[{"product":"daybyday","vendor":"daybydaycrm"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"In DayByDay CRM, versions 2.2.0 through 2.2.1 (latest) are vulnerable to Insufficient Session Expiration. When a password has been changed by the user or by an administrator, a user that was already logged in, will still have access to the application even after the password was changed.","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":"DayByDay CRM - Insufficient Session Expiration after Password Change","id":"CVE-2022-22113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Teedy - Reflected Cross-Site Scripting (XSS) in the Search Functionality","id":"CVE-2022-22114"},"packages":[],"prev":{"headline":"DayByDay CRM - Application-Wide Client-Side Template Injection (CSTI)","id":"CVE-2022-22112"},"products":["DaybydayCRM"],"published":"2022-01-13","related":[{"cvss_score":5.4,"headline":"DayByDay CRM - Application-Wide Client-Side Template Injection (CSTI)","id":"CVE-2022-22112","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-35704","kev_date_added":null,"published":"2020-12-25"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-35705","kev_date_added":null,"published":"2020-12-25"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-35706","kev_date_added":null,"published":"2020-12-25"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-35707","kev_date_added":null,"published":"2020-12-25"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Bottelet"]},"summary":"Attackers can maintain access to DayByDay CRM after a password change because existing sessions are not invalidated.","url":"https://insights.sbomify.com/CVE-2022-22113/"}