EUVD-2026-85848
GHSA-mfvg-gv48-78hw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local unprivileged access
-
DeliveryPlant malicious wtsapi32.dll in C:\ProgramData\Evope\
-
ExploitTrigger/await Evope.Service.exe restart
-
ExecutionService loads DLL as SYSTEM
-
ImpactExecute code with SYSTEM privileges
Vulnerability Assessment
| Exploitation Conditions | Requires local access to a Windows host running Evope Collector below 1.1.7.13, plus write permission to the C:\ProgramData\Evope\ directory to plant a file named wtsapi32.dll. Exploitation is limited by: the need for prior local presence (AV:L, no network path); the requirement that Evope.Service.exe subsequently start or restart to load the malicious DLL (reflected as AT:P); and the DLL name/path being fixed. There is no user-interaction requirement on a victim. Non-default hardening of ACLs on C:\ProgramData\Evope\ would block the file placement. |
| Impact | This is a local privilege-escalation flaw (uncontrolled search path / DLL planting) in Evope Collector prior to 1.1.7.13. The CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:N/UI:N) confirms a LOCAL attack vector with an attack requirement (AT:P), not a remotely reachable issue - so despite the 7.5 'HIGH' rating, real-world risk is gated by the attacker first having local access to the host. Impact is genuinely severe once triggered: the vulnerable Evope.Service.exe runs as NT AUTHORITY\SYSTEM and loads an attacker-supplied wtsapi32.dll, yielding VC:H/VI:H/VA:H (full SYSTEM compromise). No EPSS score, no CISA KEV listing, and no public exploit code are present in the provided data, so exploitation status is 'no public exploit identified at time of analysis' - this is a patch-priority-by-impact issue on affected hosts rather than a mass-exploited internet-facing threat. Note the 'RCE' tag overstates reach: with AV:L this is local code execution/LPE, not network RCE. Conflict to verify: the vector states PR:N (no privileges) while the technique realistically requires a local user session able to write to C:\ProgramData\Evope\ - treat as a low-privileged local user prerequisite. |
| Exploit ScenarioDerived | A low-privileged local user (or malware already running as a standard user) drops a malicious wtsapi32.dll into the writable C:\ProgramData\Evope\ directory. When the SYSTEM-level Evope.Service.exe next starts or restarts, it loads the planted DLL from that insecure search path and executes the attacker's code as NT AUTHORITY\SYSTEM. No public exploit code is identified, but the DLL-planting technique is trivial and well-understood. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
Local privilege escalation in Evope Collector (all versions before 1.1.7.13) lets an attacker who already has a local foothold with write access to C:\ProgramData\Evope\ plant a file named wtsapi32.dll that Evope.Service.exe, running as NT AUTHORITY\SYSTEM, loads without validating its origin, resulting in arbitrary code execution with SYSTEM privileges. The weakness is an uncontrolled search path element in the service's DLL loading, so exploitation requires no victim interaction, though the service must start or restart before the planted library is loaded (captured as AT:P in the 7.5 CVSS 4.0 vector). No public exploit code or CISA KEV entry was identified at time of analysis, and the vendor has published a fixed version, 1.1.7.13.
RemediationAI
Vendor-released patch: update Evope Collector to 1.1.7.13 or later, as documented in the INCIBE advisory (https://www.incibe.es/en/incibe-cert/notices/aviso/uncontrolled-search-path-element-evope-collector), which is the only patch reference provided and should be consulted for distribution-specific artifacts and install steps; patching is the only measure that removes the flawed module-resolution behavior itself. Where an immediate upgrade is not possible, harden C:\ProgramData\Evope\ so unprivileged local users cannot create files there - disable ACL inheritance on the folder, remove CREATOR OWNER and write permissions granted to Authenticated Users, Users and any interactive group, and grant write access only to the Evope service account and administrators. Trade-off: this can break the collector if its service legitimately writes logs, configuration or state under that directory, so the ACL should be scoped to the service account rather than removed wholesale and then regression-tested. Additional compensating controls with low cost: monitor for the creation of wtsapi32.dll inside C:\ProgramData\Evope\ (the filename is fixed, so a simple file-integrity or EDR rule is effective), periodically audit the directory's permissions for regression, and recognize that the AT:P factor in the vendor vector means a service restart is the trigger - deferring or scheduling restarts only after an integrity scan reduces the window, but does not fix the underlying uncontrolled search path weakness.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-427, uncontrolled search path element - the classic Windows DLL-planting (binary planting) weakness. wtsapi32.dll is a legitimate Microsoft Remote Desktop Services library; Evope.Service.exe apparently resolves that module by name without a fully qualified path, so the OS loader consults directories on the search path that are writable by ordinary users. C:\ProgramData\Evope\ is both part of that search order for the service and, by default, writable to the account that creates content under ProgramData via inherited CREATOR OWNER and Users ACLs, which is exactly the precondition the exploit needs. Because the host process runs as NT AUTHORITY\SYSTEM, the planted DLL executes with SYSTEM integrity rather than in the attacker's user context, converting a file-placement primitive into a full local privilege escalation (confidentiality, integrity and availability all rated high per the vendor vector and the independent assessment). The CPE cpe:2.3:a:evope_collector:evope_collector:*:*:*:*:*:*:*:* is version-agnostic and, combined with the description, is bounded at versions below 1.1.7.13; the DLL name and directory are fixed, and the attack surface is limited to the local host (no network vector), with the additional precondition that the service load the module after the file is dropped.
Know when Evope Collector gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Local DLL planting needs a low-privileged local session with write access to ProgramData (PR:L, AV:L); SYSTEM execution yields full C:H/I:H/A:H with no scope change.
Primary rating from Vendor (INCIBE).
CVSS VectorVendor: INCIBE
DescriptionCVE.org
a vulnerability involving an unchecked search path element in Evope Collector, versions prior to 1.1.7.13, allows a local attacker without privileges to load a malicious DLL by placing a ‘wtsapi32.dll’ file in the ‘C:\ProgramData\Evope\’ directory. The ‘Evope.Service.exe’ component, which runs with ‘NT AUTHORITY\SYSTEM’ privileges, loads this DLL without properly verifying its integrity or origin. Successful exploitation could allow code execution with SYSTEM privileges and result in local privilege escalation.
Executive ViewAI
A high-severity local privilege escalation flaw affects Evope Collector, a Windows endpoint agent, on all versions prior to 1.1.7.13; an attacker who already holds a limited local foothold on a host can leverage it to run code as NT AUTHORITY\SYSTEM and take full control of that machine. The exposure is confined to devices where Evope Collector is installed and where an attacker has already achieved local write access, so this is primarily an escalation and lateral-movement enabler rather than a remote entry point. Leadership should care because SYSTEM-level compromise of managed endpoints can lead to credential theft, tampering with security tooling, and broader domain-wide impact if privileged accounts are harvested.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Exploit-DB