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

CVE-2025-10089

HIGH · 7.7 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
No privileges

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
Uncontrolled Search Path Element Vulnerability in Setting and Operation Application for Lighting Control System MILCO.S Setting Application all versions, MILCO.S Setting Application (IR) all versions, MILCO.S Easy Setting Application (IR) all versions, and MILCO.S Easy Switch Application (IR) all versions allows a local attacker to execute malicious code by having installer to load a malicious DLL. However, if the signer name "Mitsubishi Electric Lighting" appears on the "Digital Signatures" tab of the properties for "MILCO.S Lighting Control.exe", the application is a fixed one. This vulnerability only affects when the installer is run, not after installation. If a user downloads directly from Mitsubishi Electric website and installs the affected product, there is no risk of malicious code being introduced.

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

This is a DLL hijacking vulnerability (uncontrolled search path element) in the installer for MILCO.S Lighting Control applications. A local attacker can place a malicious DLL in a directory searched by the installer, causing arbitrary code execution during the installation process.

MitigationEnsure the installer is properly signed with 'Mitsubishi Electric Lighting' certificate and only download installers from the official Mitsubishi Electric website to avoid tampered versions.

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/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 checks

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

  1. Identify MILCO.S Lighting Control installation
    Check Windows installed programs (Add/Remove Programs, registry HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or use 'Get-ItemProperty' PowerShell command on that registry path) for entries containing 'MILCO.S' or 'Mitsubishi' lighting control software
    Affected if MILCO.S Lighting Control application appears in installed programs list
  2. Locate installer or uninstaller executable
    Search for installer files in typical locations: %ProgramFiles%\MILCO.S, %ProgramFiles%\Mitsubishi Electric, or check the original installer location. Look for setup.exe, install.exe, or uninstall.exe files with names referencing MILCO.S or Mitsubishi Lighting
    Affected if Installer or uninstaller executable exists on the system
  3. Verify installer digital signature
    Right-click the installer/uninstaller exe file, select Properties, go to Digital Signatures tab. Verify the certificate issuer is 'Mitsubishi Electric Lighting' and the signature is valid (not expired, not revoked)
    Affected if Installer lacks valid 'Mitsubishi Electric Lighting' digital signature or shows signature error
  4. Check for suspicious DLLs in search paths
    Examine directories where installer was run from (installation directory, %TEMP%, current working directory at install time, Windows system directories) for unknown or recently placed DLLs with names that might be hijacked (e.g., bcrypt.dll, crypt32.dll, version.dll, or other common DLL names)
    Affected if Unexpected DLL files exist in installation directory or temp directories that were not part of the original installer package
  5. Review installation logs for DLL load attempts
    Check Windows installer logs (typically in %TEMP% with MSI*.log naming, or %WINDIR%\INF\setupapi.dev.log) for entries showing DLL search paths and attempted loads during MILCO.S installation
    Affected if Logs show DLL loads from untrusted paths or failed signature validation attempts

If MILCO.S Lighting Control is installed and its installer lacks a valid 'Mitsubishi Electric Lighting' digital signature, the system may have been compromised via this DLL hijacking vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure the installer is properly signed with 'Mitsubishi Electric Lighting' certificate and only download installers from the official Mitsubishi Electric website to avoid tampered versions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10089 — 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-10089 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