CVE-2016-20059

Iobit Malware Fighter privilege escalation

7.8 HIGHPublic exploitEPSS 0.18%

Published4 Apr 2026

Description

IObit Malware Fighter 4.3.1 contains an unquoted service path vulnerability in the IMFservice and LiveUpdateSvc services that allows local attackers to escalate privileges. Attackers can insert a malicious executable file in the unquoted service path and trigger privilege escalation when the service restarts or the system reboots, executing code with LocalSystem privileges.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Iobit Malware Fighter≤ 4.3.1

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://www.exploit-db.com/exploits/40525ExploitVDB Entry
https://www.vulncheck.com/advisories/iobit-malware-fighter-unquoted-service-path-privilege-escalationThird Party Advisory
http://www.iobit.com/downloadcenter.php?product=malware-fighter-freeProduct
http://www.iobit.com/en/index.phpProduct

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2016-20059 being actively exploited?

CVE-2016-20059 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.18%.

How severe is CVE-2016-20059?

CVE-2016-20059 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.18% probability of exploitation.

Which products are affected by CVE-2016-20059?

Affected products include Iobit Malware Fighter.

How do I fix CVE-2016-20059?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2016-20059 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.