# CVE-2025-49148: ClipShare Server Allows Local Privilege Escalation via DLL Hijacking

> Local attackers can escalate privileges to Administrator by placing malicious DLLs in the application directory due to insecure DLL search order.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** GHSA-rc47-h83g-2r8j

## What is CVE-2025-49148?

CVE-2025-49148 is a high-severity vulnerability in thevindu-w clip_share_server, published on 11 Jun 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.

### Official description

ClipShare is a lightweight and cross-platform tool for clipboard sharing. Prior to 3.8.5, ClipShare Server for Windows uses the default Windows DLL search order and loads system libraries like CRYPTBASE.dll and WindowsCodecs.dll from its own directory before the system path. A local, non-privileged user who can write to the folder containing clip_share.exe can place malicious DLLs there, leading to arbitrary code execution in the context of the server, and, if launched by an Administrator (or another elevated user), it results in a reliable local privilege escalation. This vulnerability is fixed in 3.8.5.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2025-49148 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49148 is a high-severity vulnerability in thevindu-w clip_share_server, published on 11 Jun 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49148 exists.

Affected product: thevindu-w clip_share_server. 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-49148/ (Markdown: https://insights.sbomify.com/CVE-2025-49148/index.md)
```

## Sources

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

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