dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-10549

MEDIUM · 5.1 CVSS v3.1 Published 2026-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
53/100
Remediation priority · Moderate
Zero-click

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 · unedited
EfficientLab Controlio before v1.3.95 contains a DLL hijacking vulnerability caused by weak folder permissions in the installation directory. A local attacker can place a specially crafted DLL in this directory and achieve arbitrary code execution with highest privileges, because the affected service runs as NT AUTHORITY\SYSTEM.

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 confidence

EfficientLab Controlio before v1.3.95 suffers from DLL hijacking due to weak folder permissions in the installation directory. A local attacker can place a malicious DLL that the application will load, achieving arbitrary code execution with NT AUTHORITY\SYSTEM privileges since the service runs under that account.

MitigationRestrict folder permissions on the Controlio installation directory to prevent unauthorized file placement, and upgrade to v1.3.95 or later which should implement secure DLL loading.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Controlio installation directory
    Check the program files folders (typically C:\Program Files\EfficientLab or C:\Program Files (x86)\EfficientLab) for the Controlio application folder, or query the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the InstallLocation value
    Affected if The installation directory cannot be found or Controlio is not installed, then the system is not affected by this specific vulnerability
  2. Determine the installed Controlio version
    Right-click the main Controlio executable (typically named Controlio.exe or similar) in the installation folder, select Properties, and view the File Version on the Details tab, or use PowerShell: (Get-Item 'C:\Path\To\Controlio.exe').VersionInfo.FileVersion
    Affected if The version is lower than v1.3.95 (for example, v1.3.90, v1.3.80, etc.) indicating the installation is vulnerable
  3. Verify folder permissions on the installation directory
    Right-click the Controlio installation folder, go to Properties > Security tab, and examine the permissions for Users and Authenticated Users groups, or run: icacls 'C:\Path\To\Controlio' to list effective permissions
    Affected if Users or Authenticated Users have Write or CreateFiles permissions on the folder, allowing a local attacker to place a malicious DLL
  4. Confirm the Controlio service runs under NT AUTHORITY\SYSTEM
    Open Services (services.msc), locate the Controlio service, right-click and select Properties, and check the Log On account, or run: Get-Service -Name 'Controlio' | Select-Object -Property Name, @{N='Account';E={(Get-WmiObject Win32_Service -Filter "Name='$($_.Name)'").StartName}}
    Affected if The service Log On account is set to NT AUTHORITY\SYSTEM, meaning successful DLL hijacking yields SYSTEM-level code execution
  5. Inspect for unexpected DLL files in the installation directory
    List all DLL files in the Controlio installation folder: dir 'C:\Path\To\Controlio\*.dll', and compare against known legitimate DLLs expected by the application (check timestamps and file origins if possible)
    Affected if There are DLLs with unusual timestamps or DLLs that do not belong to the standard Controlio installation, suggesting potential tampering

The system is affected if Controlio is installed with a version before v1.3.95 AND the installation directory has weak write permissions allowing a local user to place a malicious DLL that the service will load and execute as SYSTEM.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict folder permissions on the Controlio installation directory to prevent unauthorized file placement, and upgrade to v1.3.95 or later which should implement secure DLL loading.

Recommended fix High confidence

EfficientLab Controlio v1.3.95

  1. 1. Identify the current installed version of EfficientLab Controlio
  2. 2. If the current version is before v1.3.95, download the latest version from the vendor's official source
  3. 3. Back up the current installation and any associated configurations
  4. 4. Install Controlio v1.3.95 or later
  5. 5. Verify the installation completed successfully and the service runs correctly
  6. 6. As an additional mitigation, verify that the installation directory has restrictive permissions (only Administrators and SYSTEM should have write access)
Caveat Review release notes for any feature changes between current version and v1.3.95 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10549 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10549 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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