CVE-2016-20059 | IObit Malware Fighter 4.3.1 LiveUpdateSvc Service unquoted search path (Exploit 40525 / EDB-40525)

VDB-355371 · CVE-2016-20059 · EXPLOIT 40525 IOBIT MALWARE FIGHTER 4.3.1 LIVEUPDATESVC SERVICE UNQUOTED SEARCH PATH HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.1 $0-$5k 1.38+ Summaryinfo A vulnerability identified as problematic has been detected in IObit Malware Fighter 4.3.1. Impacted is an unknown function of the component LiveUpdateSvc Service. Performing a manipulation results in unquoted search path. This vulnerability is identified as CVE-2016-20059. The attack is only possible with local access. Additionally, an exploit exists. Detailsinfo A vulnerability was found in IObit Malware Fighter 4.3.1. It has been classified as critical. This affects some unknown functionality of the component LiveUpdateSvc Service. The manipulation with an unknown input leads to a unquoted search path vulnerability. CWE is classifying the issue as CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: 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. The weakness was released by Amir.ght as 40525. It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2016-20059 since 04/04/2026. The exploitability is told to be difficult. Attacking locally is a requirement. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1574.009 according to MITRE ATT&CK. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. The vulnerability is also documented in the vulnerability database at Exploit-DB (40525). Productinfo Type Anti-Malware Software Vendor IObit Name Malware Fighter Version 4.3.1 License free CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.4 VulDB Meta Temp Score: 7.1 VulDB Base Score: 7.0 VulDB Temp Score: 6.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.8 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Unquoted search path CWE: CWE-428 / CWE-426 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Exploit-DB: 🔒 Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/04/2026 Advisory disclosed 04/04/2026 +0 days CVE reserved 04/04/2026 +0 days VulDB entry created 04/04/2026 +0 days VulDB entry last update Sourcesinfo Advisory: 40525 Researcher: Amir.ght Status: Not defined CVE: CVE-2016-20059 (🔒) GCVE (CVE): GCVE-0-2016-20059 GCVE (VulDB): GCVE-100-355371 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/04/2026 19:48 Changes: 04/04/2026 19:48 (81) Complete: 🔍 Cache ID: 99:BB5:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸