{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-27106 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27106 is a high-severity command injection vulnerability in chrisleekr binance-trading-bot, published on 21 Feb 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-27106 and fix it if it is affected.\n\nWhat it is: CVE-2025-27106 is a high-severity command injection vulnerability in chrisleekr binance-trading-bot, published on 21 Feb 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-27106 in the wild and no public exploit code.\n\nAffected product: chrisleekr binance-trading-bot. 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-27106/ (Markdown: https://insights.sbomify.com/CVE-2025-27106/index.md)","id":"CVE-2025-27106","markdown":"https://insights.sbomify.com/CVE-2025-27106/index.md","name":"CVE-2025-27106","record":{"aliases":["GHSA-wq6j-4388-4gg5"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Binance trading bot","requires_auth":"low_privilege","summary":"Authenticated users can execute arbitrary code on the host via command injection in the restore endpoint of the Binance trading bot.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"binance-trading-bot is an automated Binance trading bot with trailing buy/sell strategy. Authenticated users of binance-trading-bot can achieve Remote Code Execution on the host system due to a command injection vulnerability in the `/restore` endpoint. The restore endpoint of binance-trading-bot is vulnerable to command injection via the `/restore` endpoint. The name of the uploaded file is passed to shell.exec without sanitization other than path normalization, resulting in Remote Code Execution. This may allow any authorized user to execute code in the context of the host machine. This issue has been addressed in version 0.0.100 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in binance-trading-bot","id":"CVE-2025-27106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Integrated Scripting vulnerable to arbitrary code execution via Java reflection","id":"CVE-2025-27107"},"packages":[],"prev":{"headline":"AugAssign evaluation order causing OOB write within the object in Vyper","id":"CVE-2025-27105"},"products":["binance-trading-bot"],"published":"2025-02-21","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":"total"},"state":"PUBLISHED","updated":"2025-02-22","vendors":["chrisleekr"]},"summary":"Authenticated users can execute arbitrary code on the host via command injection in the restore endpoint of the Binance trading bot.","url":"https://insights.sbomify.com/CVE-2025-27106/"}