Dr.foneApplication · Wondershare

CVE-2021-44595

HIGH · 8.8 CVSS v3.1 Published 2022-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
Wondershare Dr. Fone Latest version as of 2021-12-06 is vulnerable to Incorrect Access Control. A normal user can send manually crafted packets to the ElevationService.exe and execute arbitrary code without any validation with SYSTEM privileges.

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 confidence

Wondershare Dr. Fone's ElevationService.exe runs with SYSTEM privileges but lacks proper access control validation. A normal (unprivileged) user can send manually crafted packets directly to this service to execute arbitrary code with elevated privileges, resulting in local privilege escalation.

MitigationApply the vendor patch from Wondershare when available. In the interim, restrict user access to the Dr. Fone application directory and monitor for suspicious connections to ElevationService.exe.

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
Dr.foneApplication
Affected:= 2021-12-06

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

CVSS:3.1/AV:N/AC:L/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. Verify if Wondershare Dr. Fone is installed
    Check common installation paths or search for Dr. Fone in Add/Remove Programs. Look for directories containing 'Dr. Fone' or 'Wondershare' in Program Files or Program Files (x86).
    Affected if Dr. Fone version 2021-12-06 is found installed on the system
  2. Confirm the installed Dr. Fone version
    Locate the Dr. Fone installation directory and check for version information in the application properties, an About dialog, or version file within the program folder.
    Affected if The installed version matches exactly 2021-12-06
  3. Identify if ElevationService.exe exists
    Search for ElevationService.exe within the Dr. Fone installation directory or subdirectories.
    Affected if ElevationService.exe is present in the Dr. Fone installation folder
  4. Check if the ElevationService is running
    Open Services console (services.msc) or run 'sc query' to check for a service related to Dr. Fone ElevationService, or check running processes for ElevationService.exe.
    Affected if The ElevationService is installed and running on the system
  5. Verify service configuration and permissions
    Run 'sc qc' or examine the service binary path using 'sc enumdepend' to confirm it runs with elevated privileges. Check file permissions on ElevationService.exe to see if unprivileged users can interact with it.
    Affected if The service runs with SYSTEM or elevated privileges and lacks proper access control checks

The system is affected if Wondershare Dr. Fone version 2021-12-06 is installed with the ElevationService.exe running and accessible to unprivileged users.

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

Apply the vendor patch from Wondershare when available. In the interim, restrict user access to the Dr. Fone application directory and monitor for suspicious connections to ElevationService.exe.

Fix this in Dr.fone Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-44595 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-44595 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