{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45746 exists.","fix":"No fix has been published for CVE-2025-45746 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45746 is a medium-severity vulnerability in ZKTeco ZKBio CVSecurity, published on 13 May 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-45746 and fix it if it is affected.\n\nWhat it is: CVE-2025-45746 is a medium-severity vulnerability in ZKTeco ZKBio CVSecurity, published on 13 May 2025. 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-2025-45746 exists.\n\nAffected product: ZKTeco ZKBio CVSecurity. 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-45746/ (Markdown: https://insights.sbomify.com/CVE-2025-45746/index.md)","id":"CVE-2025-45746","markdown":"https://insights.sbomify.com/CVE-2025-45746/index.md","name":"CVE-2025-45746","record":{"aliases":["GHSA-rcw6-7x98-m9g9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ZKTeco security software","requires_auth":"none","summary":"An unauthenticated attacker can bypass authentication to the service console by crafting a JWT token using a hardcoded secret.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zkbio_cvsecurity","vendor":"zkteco"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"In ZKT ZKBio CVSecurity 6.4.1_R an unauthenticated attacker can craft JWT token using the hardcoded secret to authenticate to the service console. NOTE: the Supplier disputes the significance of this report because the service console is typically only accessible from a local area network, and because access to the service console does not result in login access or data access in the context of the application software platform.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in ZKBio CVSecurity","id":"CVE-2025-45746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-45751"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-45737"},"products":["ZKBio CVSecurity"],"published":"2025-05-13","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-36526","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2024-35430","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":8.1,"headline":"Privilege escalation in n/a","id":"CVE-2024-35433","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2024-35431","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":7.1,"headline":"Path traversal in n/a","id":"CVE-2024-35428","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2024-35429","kev_date_added":null,"published":"2024-05-30"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-21","vendors":["ZKTeco"]},"summary":"An unauthenticated attacker can bypass authentication to the service console by crafting a JWT token using a hardcoded secret.","url":"https://insights.sbomify.com/CVE-2025-45746/"}