CVE-2025-61161
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 · uneditedDLL 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.
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 confidenceEvope.Service.exe, running with SYSTEM privileges, loads wtsapi32.dll from an uncontrolled search path (C:\ProgramData\Evope). Local unprivileged attackers can place a crafted malicious DLL in this directory to achieve arbitrary code execution with SYSTEM-level privileges during service startup or reboot.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Evope.Service.exe is presentSearch for Evope.Service.exe on the system using: Get-ChildItem -Path C:\ -Filter "Evope.Service.exe" -Recurse -ErrorAction SilentlyContinue or check installed programs for Evope softwareAffected if Evope.Service.exe is found on the system, indicating the affected software is installed
-
Confirm C:\ProgramData\Evope directory existsCheck if the directory exists: Test-Path "C:\ProgramData\Evope"Affected if The directory C:\ProgramData\Evope exists, creating the condition for DLL planting
-
Check if directory is writable by unprivileged usersRun: Get-Acl "C:\ProgramData\Evope" | Select-Object -ExpandProperty Access to view permissions, or attempt to create a test file in that directory from a standard user accountAffected if Standard users or the Everyone group has Write or Modify permissions on C:\ProgramData\Evope, allowing attackers to place malicious DLLs
-
Verify service runs with SYSTEM privilegesRun: Get-Service -Name EvopeService -ErrorAction SilentlyContinue | Get-WmiObject Win32_Service to check the StartName property, or check via services.mscAffected if The Evope service is configured to run as LocalSystem or a SYSTEM-level account, meaning privilege escalation to SYSTEM is possible
-
Confirm wtsapi32.dll is loaded by the serviceUse Process Explorer or run: tasklist /m /fi "imagename eq Evope.Service.exe" to list loaded modules, or monitor DLL loading during service startupAffected if Evope.Service.exe loads wtsapi32.dll from the application directory rather than system paths
The environment is affected if Evope.Service.exe is installed, C:\ProgramData\Evope exists, and that directory is writable by unprivileged users, allowing DLL planting for SYSTEM-level code execution.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict write access to C:\ProgramData\Evope to privileged users only, or modify Evope.Service.exe to use safe DLL loading practices (specify absolute path, use LOAD_LIBRARY_SEARCH_SYSTEM_ONLY, or enable safe DLL search mode).
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61161 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61161 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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