{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59451 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59451 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59451 is a low-severity vulnerability in YoSmart YoLink application, published on 6 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59451 and fix it if it is affected.\n\nWhat it is: CVE-2025-59451 is a low-severity vulnerability in YoSmart YoLink application, published on 6 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59451 in the wild and no public exploit code.\n\nAffected product: YoSmart YoLink application. 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-59451/ (Markdown: https://insights.sbomify.com/CVE-2025-59451/index.md)","id":"CVE-2025-59451","markdown":"https://insights.sbomify.com/CVE-2025-59451/index.md","name":"CVE-2025-59451","record":{"aliases":["GHSA-ww8q-926q-45p7"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"YoLink mobile app","requires_auth":"low_privilege","summary":"Attackers can hijack user accounts due to excessively long session token lifetimes in the YoLink mobile application.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The YoSmart YoLink application through 2025-10-02 has session tokens with unexpectedly long lifetimes.","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":"Security feature bypass in YoLink application","id":"CVE-2025-59451","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Weak cryptography in YoLink API","id":"CVE-2025-59452"},"packages":[],"prev":{"headline":"Hardcoded credentials in YoLink Smart Hub","id":"CVE-2025-59450"},"products":["YoLink application"],"published":"2025-10-06","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":"2025-11-26","vendors":["YoSmart"]},"summary":"Attackers can hijack user accounts due to excessively long session token lifetimes in the YoLink mobile application.","url":"https://insights.sbomify.com/CVE-2025-59451/"}