{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-62717 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62717 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62717 is a low-severity authentication bypass vulnerability in Emlog Emlog, published on 24 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62717 and fix it if it is affected.\n\nWhat it is: CVE-2025-62717 is a low-severity authentication bypass vulnerability in Emlog Emlog, published on 24 Oct 2025. 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-2025-62717 in the wild and no public exploit code.\n\nAffected product: Emlog Emlog. 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-2025-62717/ (Markdown: https://insights.sbomify.com/CVE-2025-62717/index.md)","id":"CVE-2025-62717","markdown":"https://insights.sbomify.com/CVE-2025-62717/index.md","name":"CVE-2025-62717","record":{"aliases":["GHSA-wwj4-ppfj-hcm6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Emlog CMS","requires_auth":"none","summary":"Attackers can reuse email verification codes due to a clearing logic error, potentially bypassing authentication in Emlog Pro.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"emlog","vendor":"emlog"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Emlog is an open source website building system. In version 2.5.23, Emlog Pro is vulnerable to a session verification code error due to a clearing logic error. This means the verification code could be reused anywhere an email verification code is required. This issue has been fixed in commit 1f726df.","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":"Emlog Pro session verification code error due to clearing logic error","id":"CVE-2025-62717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"emlog:emlog","products":["emlog:emlog"],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF","id":"CVE-2025-62718"},"packages":[],"prev":{"headline":"Plane Vulnerable to Cross-Site Scripting via Open Redirect in ?next_path Parameter","id":"CVE-2025-62716"},"products":["emlog"],"published":"2025-10-24","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-29401","kev_date_added":null,"published":"2025-03-19"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-25783","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-44973","kev_date_added":null,"published":"2023-10-03"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-44974","kev_date_added":null,"published":"2023-10-03"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2023-43291","kev_date_added":null,"published":"2023-09-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-23379","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-40883","kev_date_added":null,"published":"2021-12-14"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-24","vendors":["emlog"]},"summary":"Attackers can reuse email verification codes due to a clearing logic error, potentially bypassing authentication in Emlog Pro.","url":"https://insights.sbomify.com/CVE-2025-62717/"}