dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-10541

HIGH · 7.8 CVSS v3.1 Published 2025-09-25
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
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
iMonitor EAM 9.6394 installs a system service (eamusbsrv64.exe) that runs with NT AUTHORITY\SYSTEM privileges. This service includes an insecure update mechanism that automatically loads files placed in the C:\sysupdate\ directory during startup. Because any local user can create and write to this directory, an attacker can place malicious DLLs or executables in it. Upon service restart, the files are moved to the application’s installation path and executed with SYSTEM privileges, leading to privilege escalation.

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

iMonitor EAM 9.6394 installs a system service (eamusbsrv64.exe) running with NT AUTHORITY\SYSTEM privileges that contains an insecure update mechanism. The service automatically loads and moves files from the C:\sysupdate\ directory—which is world-writable—into the application's installation path and executes them with SYSTEM privileges upon startup, allowing any local user to escalate to SYSTEM.

MitigationDisable the eamusbsrv64.exe service or remove world-write permissions from C:\sysupdate\, and contact the vendor for a patched version that addresses this insecure update mechanism.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check if iMonitor EAM is installed and identify its version
    Check the installation directory (typically C:\Program Files\iMonitor\EAM or similar) for the iMonitor EAM application files. Look for version information in the program's properties, README, or an About section. Alternatively, check the Windows Programs and Features list for iMonitor EAM and note the installed version.
    Affected if The installed version is 9.6394 or falls within the affected version range.
  2. Verify the eamusbsrv64.exe service exists
    Open Services (services.msc) and look for a service related to eamusbsrv64.exe, or run 'sc query' to enumerate services and search for one containing 'eamusbsrv' or 'usb' in the name. You can also check the Task Manager or use 'tasklist /svc' to find the running service.
    Affected if The eamusbsrv64.exe service is present and running on the system.
  3. Confirm the service runs with SYSTEM privileges
    In Services, right-click the eamusbsrv64.exe service, go to Properties, and check the 'Log on as' field. Alternatively, use 'sc qc <servicename>' or 'sc x ShowingAll' from an elevated command prompt to view the service configuration.
    Affected if The service is configured to run as NT AUTHORITY\SYSTEM or the Local System account.
  4. Check if the C:\sysupdate\ directory exists
    Open File Explorer or use the command prompt to navigate to C:\sysupdate\. Run 'dir C:\sysupdate\' or 'ls /mnt/c/sysupdate/' depending on your environment. If the directory does not exist, the vulnerability may not be exploitable in its current state, but the insecure mechanism may still be present.
    Affected if The C:\sysupdate\ directory exists on the system.
  5. Verify permissions on the C:\sysupdate\ directory
    Right-click the C:\sysupdate\ folder in File Explorer, select Properties, then go to the Security tab. Check which users and groups have permissions, particularly looking for 'Users' or 'Everyone' with Write or Modify permissions. From command line, run 'icacls C:\sysupdate\' to view the ACL.
    Affected if The C:\sysupdate\ directory has world-writable permissions (Users, Everyone, or similar group has Write or Modify access), allowing any local user to place files there.

A system is affected if iMonitor EAM version 9.6394 (or an affected version range) is installed with the eamusbsrv64.exe service running as SYSTEM and the C:\sysupdate\ directory exists with world-writable permissions, enabling any local user to place executable files for SYSTEM-level execution.

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

Disable the eamusbsrv64.exe service or remove world-write permissions from C:\sysupdate\, and contact the vendor for a patched version that addresses this insecure update mechanism.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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