CVE-2025-49148
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedClipShare 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceClipShare Server for Windows versions before 3.8.5 is vulnerable to DLL hijacking. The application uses the default Windows DLL search order and loads system libraries (CRYPTBASE.dll, WindowsCodecs.dll) from its own directory before checking system paths. A local non-privileged user with write access to the clip_share.exe directory can place malicious DLLs to achieve arbitrary code execution, which escalates to privilege escalation when an administrator runs the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate ClipShare Server installationSearch for clip_share.exe on the system using File Explorer search or command: dir /s /b C:\clip_share.exe 2>nulAffected if clip_share.exe is found on the system
-
Determine installed versionRight-click clip_share.exe, select Properties, then look at the Version tab to find the product version. Compare it to 3.8.5Affected if The version is lower than 3.8.5 (e.g., 3.8.4, 3.8.0, etc.)
-
Check write permissions on application directoryRight-click the folder containing clip_share.exe, select Properties, go to Security tab, and check permissions for Users or non-admin accounts. Alternatively, run: icacls "C:\path\to\clip_share.exe" | findstr /i "Users"Affected if Users or non-privileged accounts have Write or Modify permissions to the directory
-
Verify DLL search order vulnerabilityInspect the application binary for DLL dependencies using Dependency Walker or: dumpbin /dependents clip_share.exe 2>nul. Check if CRYPTBASE.dll or WindowsCodecs.dll are loaded from the application directoryAffected if The application loads CRYPTBASE.dll or WindowsCodecs.dll and runs with elevated privileges
If ClipShare Server version is below 3.8.5 and non-privileged users can write to the clip_share.exe directory, the system is vulnerable to DLL hijacking privilege escalation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to ClipShare Server version 3.8.5 or later. Until then, restrict write access to the directory containing clip_share.exe to prevent unauthorized DLL placement.
3.8.5
- 1. Download ClipShare version 3.8.5 or later from the official GitHub repository
- 2. Stop the ClipShare Server service if it is currently running
- 3. Back up the current ClipShare installation directory
- 4. Replace the existing clip_share.exe and associated files with the version 3.8.5 files
- 5. Restart the ClipShare Server service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49148 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data