{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-6666 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6666 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6666 is a low-severity vulnerability in motogadget mo.lock Ignition Lock, published on 29 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6666 and fix it if it is affected.\n\nWhat it is: CVE-2025-6666 is a low-severity vulnerability in motogadget mo.lock Ignition Lock, published on 29 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6666 in the wild and no public exploit code.\n\nAffected product: motogadget mo.lock Ignition Lock. 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-6666/ (Markdown: https://insights.sbomify.com/CVE-2025-6666/index.md)","id":"CVE-2025-6666","markdown":"https://insights.sbomify.com/CVE-2025-6666/index.md","name":"CVE-2025-6666","record":{"aliases":["GHSA-x92v-4f2v-7xr4"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Motorcycle ignition lock","requires_auth":"none","summary":"Attackers can bypass the ignition lock security by exploiting a hard-coded cryptographic key in the NFC handler of the motogadget mo.lock device.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"description":"A vulnerability was determined in motogadget mo.lock Ignition Lock up to 20251125. Affected by this vulnerability is an unknown functionality of the component NFC Handler. Executing a manipulation can lead to use of hard-coded cryptographic key\r . The physical device can be targeted for the attack. A high complexity level is associated with this attack. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.","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":"motogadget mo.lock Ignition Lock NFC hard-coded key","id":"CVE-2025-6666","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"code-projects Car Rental System add_cars.php unrestricted upload","id":"CVE-2025-6667"},"packages":[],"prev":{"headline":"code-projects Inventory Management System editBrand.php sql injection","id":"CVE-2025-6665"},"products":["mo.lock Ignition Lock"],"published":"2025-11-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["motogadget"]},"summary":"Attackers can bypass the ignition lock security by exploiting a hard-coded cryptographic key in the NFC handler of the motogadget mo.lock device.","url":"https://insights.sbomify.com/CVE-2025-6666/"}