{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-56400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-56400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56400 is a high-severity vulnerability in n/a, published on 24 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-56400 and fix it if it is affected.\n\nWhat it is: CVE-2025-56400 is a high-severity vulnerability in n/a, published on 24 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-56400 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-2025-56400/ (Markdown: https://insights.sbomify.com/CVE-2025-56400/index.md)","id":"CVE-2025-56400","markdown":"https://insights.sbomify.com/CVE-2025-56400/index.md","name":"CVE-2025-56400","record":{"aliases":["GHSA-6w4j-qm3c-h3vj"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["account_takeover","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Tuya Smart SDK","requires_auth":"none","summary":"Attackers can link their Alexa account to victims' Tuya accounts via CSRF, enabling remote control of connected smart home devices.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smartlife","vendor":"tuya"},{"product":"tuya","vendor":"tuya"},{"product":"tuya_smart","vendor":"tuya"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in the OAuth implementation of the Tuya SDK 6.5.0 for Android and iOS, affects the Tuya Smart and Smartlife mobile applications, as well as other third-party applications that integrate the SDK, allows an attacker to link their own Amazon Alexa account to a victim's Tuya account. The applications fail to validate the OAuth state parameter during the account linking flow, enabling a cross-site request forgery (CSRF)-like attack. By tricking the victim into clicking a crafted authorization link, an attacker can complete the OAuth flow on the victim's behalf, resulting in unauthorized Alexa access to the victim's Tuya-connected devices. This affects users regardless of prior Alexa linkage and does not require the Tuya application to be active at the time. Successful exploitation may allow remote control of devices such as cameras, doorbells, door locks, or alarms.","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":"Cross-site request forgery in n/a","id":"CVE-2025-56400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-56401"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2025-56399"},"products":["n/a"],"published":"2025-11-24","related":[],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can link their Alexa account to victims' Tuya accounts via CSRF, enabling remote control of connected smart home devices.","url":"https://insights.sbomify.com/CVE-2025-56400/"}