{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54063 exists.","fix":"No fix has been published for CVE-2025-54063 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54063 is a high-severity code injection vulnerability in CherryHQ cherry-studio, published on 11 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-54063 and fix it if it is affected.\n\nWhat it is: CVE-2025-54063 is a high-severity code injection vulnerability in CherryHQ cherry-studio, published on 11 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54063 exists.\n\nAffected product: CherryHQ cherry-studio. 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-54063/ (Markdown: https://insights.sbomify.com/CVE-2025-54063/index.md)","id":"CVE-2025-54063","markdown":"https://insights.sbomify.com/CVE-2025-54063/index.md","name":"CVE-2025-54063","record":{"aliases":["GHSA-p6vw-w3p8-4g72"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Cherry Studio client","requires_auth":"none","summary":"Attackers can execute arbitrary code on victim machines by tricking them into clicking a malicious link that triggers the application's custom URL handler.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cherry_studio","vendor":"cherry-ai"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Cherry Studio is a desktop client that supports for multiple LLM providers. From versions 1.4.8 to 1.5.0, there is a one-click remote code execution vulnerability through the custom URL handling. An attacker can exploit this by hosting a malicious website or embedding a specially crafted URL on any website. If a victim clicks the exploit link in their browser, the app’s custom URL handler is triggered, leading to remote code execution on the victim’s machine. This issue has been patched in version 1.5.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cherry Studio One-click Remote Code Execution Vulnerability through Custom URL Handling","id":"CVE-2025-54063","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"rucio-server, rucio-ui, and rucio-webui vulnerable to insertion of X-Rucio-Auth-Token in apache access logfiles","id":"CVE-2025-54064"},"packages":[],"prev":{"headline":"WeGIA SQL Injection (Blind Time-Based) Vulnerability in id_dependente Parameter on profile_dependente.php Endpoint","id":"CVE-2025-54062"},"products":["cherry-studio"],"published":"2025-08-11","related":[{"cvss_score":9.7,"headline":"Cherry Studio allows one-click on a specific URL to cause a command to execute","id":"CVE-2025-61929","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":9.7,"headline":"Cherry Studio RCE Vulnerability Disclosure","id":"CVE-2025-54382","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":7.7,"headline":"Cherry Studio is Vulnerable to OS Command Injection during Connection with a Malicious MCP Server","id":"CVE-2025-54074","kev_date_added":null,"published":"2025-08-13"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-11","vendors":["CherryHQ"]},"summary":"Attackers can execute arbitrary code on victim machines by tricking them into clicking a malicious link that triggers the application's custom URL handler.","url":"https://insights.sbomify.com/CVE-2025-54063/"}