{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14015 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14015 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14015 is a high-severity authentication bypass vulnerability in n/a, published on 24 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-14015 and fix it if it is affected.\n\nWhat it is: CVE-2020-14015 is a high-severity authentication bypass vulnerability in n/a, published on 24 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-14015 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-14015/ (Markdown: https://insights.sbomify.com/CVE-2020-14015/index.md)","id":"CVE-2020-14015","markdown":"https://insights.sbomify.com/CVE-2020-14015/index.md","name":"CVE-2020-14015","record":{"aliases":["GHSA-9867-w377-j3vf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Navigate CMS","requires_auth":"none","summary":"Attackers can reset the password of the most recently created user by omitting the activation code during password reset.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"navigate_cms","vendor":"naviwebs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"}],"description":"An issue was discovered in Navigate CMS 2.9 r1433. When performing a password reset, a user is emailed an activation code that allows them to reset their password. There is, however, a flaw when no activation code is supplied. The system will allow an unauthorized user to continue setting a password, even though no activation code was supplied, setting the password for the most recently created user in the system (the user with the highest user id).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2020-14015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-14016"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-14014"},"products":["n/a"],"published":"2020-06-24","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-23711","kev_date_added":null,"published":"2021-06-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-17552","kev_date_added":null,"published":"2018-10-03"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2021-36455","kev_date_added":null,"published":"2021-08-06"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-17553","kev_date_added":null,"published":"2018-10-03"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2021-44351","kev_date_added":null,"published":"2022-01-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-14017","kev_date_added":null,"published":"2020-06-24"}],"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-08-04","vendors":["n/a"]},"summary":"Attackers can reset the password of the most recently created user by omitting the activation code during password reset.","url":"https://insights.sbomify.com/CVE-2020-14015/"}