Evope Collector 1.1.6.9.0 Evope.Service.exe uncontrolled search path

Summaryinfo

A vulnerability classified as problematic has been found in Evope Collector 1.1.6.9.0. The affected element is an unknown function in the library wtsapi32.dll of the file Evope.Service.exe. The manipulation leads to uncontrolled search path. This vulnerability is listed as CVE-2025-61161. The attack must be carried out locally. There is no available exploit.

Detailsinfo

A vulnerability was found in Evope Collector 1.1.6.9.0 and classified as critical. This issue affects some unknown processing in the library wtsapi32.dll of the file Evope.Service.exe. The manipulation with an unknown input leads to a uncontrolled search path vulnerability. Using CWE to declare the problem leads to CWE-427. The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

DLL hijacking vulnerability in Evope Collector 1.1.6.9.0 and related components load the wtsapi32.dll library from an uncontrolled search path (C:\ProgramData\Evope). This allows local unprivileged attackers to execute arbitrary code or escalate privileges to SYSTEM by placing a crafted DLL in that location. The vulnerable component is Evope.Service.exe, which runs with SYSTEM privileges and automatically loads the DLL on startup or reboot.

The identification of this vulnerability is CVE-2025-61161 since 09/26/2025. The exploitation is known to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/29/2025). MITRE ATT&CK project uses the attack technique T1574 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Evope

Name

• Collector

Version

• 1.1.6.9.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion