# CVE-2025-63685: Code injection in n/a

> Attackers can execute arbitrary code by placing a malicious DLL in the application's startup directory, exploiting insecure library loading.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-4wm7-8hvv-947f

## What is CVE-2025-63685?

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.

### Official 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.

Weakness: CWE-491 (Public cloneable() Method Without Final)

## Which versions are affected by CVE-2025-63685?

It affects 1 product.


Products: Quark Quark Cloud Drive.

## How do I fix CVE-2025-63685?

No fix has been published for CVE-2025-63685 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63685 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63685 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63685 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63685 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63685/ (Markdown: https://insights.sbomify.com/CVE-2025-63685/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63685
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63685
- OSV: https://osv.dev/vulnerability/CVE-2025-63685

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63685/
Summaries are generated and may contain mistakes; the official description above is the record.