dbcve.org
TodeskApplication

CVE-2025-4539

HIGH · 7.0 CVSS v3.1 Published 2025-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

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 · unedited
A vulnerability was found in Hainan ToDesk 4.7.6.3. It has been declared as critical. This vulnerability affects unknown code in the library profapi.dll of the component DLL File Parser. The manipulation leads to uncontrolled search path. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

A local DLL hijacking vulnerability exists in ToDesk 4.7.6.3's profapi.dll library used for DLL file parsing. The application loads DLLs without specifying a full path, allowing a local attacker to place a malicious DLL in the search path that gets loaded instead of the legitimate library, potentially leading to arbitrary code execution.

MitigationSince the vendor has not responded, organizations should consider removing or disabling the vulnerable ToDesk installation, implement application whitelisting controls to prevent untrusted DLL loading, and monitor for any updates from the vendor.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TodeskApplication
Affected:= 4.7.6.3

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if ToDesk is installed on the system
    Check common installation directories for ToDesk executable (e.g., C:\Program Files\ToDesk\, C:\Program Files (x86)\ToDesk\) or search for 'ToDesk.exe' using: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Recurse -Filter 'ToDesk.exe' -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
    Affected if ToDesk is found installed on the system and is version 4.7.6.3
  2. Verify the installed ToDesk version
    Right-click the ToDesk.exe file, select Properties, and check the 'File version' in the Details tab, or run: (Get-Item 'C:\Program Files\ToDesk\ToDesk.exe').VersionInfo.FileVersion
    Affected if The file version shows exactly 4.7.6.3
  3. Check for profapi.dll in ToDesk installation directory
    Search for profapi.dll within the ToDesk installation folder: Get-ChildItem -Path 'C:\Program Files\ToDesk' -Recurse -Filter 'profapi.dll' -ErrorAction SilentlyContinue
    Affected if profapi.dll exists in the ToDesk installation directory and the application loads it without a full path (vulnerable DLL search order)
  4. Determine if ToDesk is currently running
    Check for running ToDesk processes: Get-Process | Where-Object {$_.ProcessName -like '*ToDesk*'}
    Affected if ToDesk process is currently running, making the DLL hijacking vulnerability actively exploitable in the current session

You are affected if ToDesk version 4.7.6.3 is installed and running on your system, as the application loads profapi.dll without a secure full path allowing local DLL hijacking.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not responded, organizations should consider removing or disabling the vulnerable ToDesk installation, implement application whitelisting controls to prevent untrusted DLL loading, and monitor for any updates from the vendor.

Fix this in Todesk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4539 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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