{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63685 exists.","fix":"No fix has been published for CVE-2025-63685 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63685 is a critical code injection vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-63685 and fix it if it is affected.\n\nWhat it is: CVE-2025-63685 is a critical code injection vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63685 exists.\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-63685/ (Markdown: https://insights.sbomify.com/CVE-2025-63685/index.md)","id":"CVE-2025-63685","markdown":"https://insights.sbomify.com/CVE-2025-63685/index.md","name":"CVE-2025-63685","record":{"aliases":["GHSA-4wm7-8hvv-947f"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud Drive Client","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious DLL in the application's startup directory, exploiting insecure library loading.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"quark_cloud_drive","vendor":"quark"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-491","name":"Public cloneable() Method Without Final"}],"description":"Quark Cloud Drive v3.23.2 has a DLL Hijacking vulnerability. This vulnerability stems from the insecure loading of system libraries. Specifically, the application does not validate the path or signature of [regsvr32.exe] it loads. An attacker can place a crafted malicious DLL in the application's startup directory, which will be loaded and executed when the user launches the program.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2025-63685","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2025-63686"},"packages":[],"prev":{"headline":"open-webui is Vulnerable to Incorrect Access Control","id":"CVE-2025-63681"},"products":["n/a"],"published":"2025-11-20","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-21","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by placing a malicious DLL in the application's startup directory, exploiting insecure library loading.","url":"https://insights.sbomify.com/CVE-2025-63685/"}