dbcve.org
PcmanagerApplication · Lenovo

CVE-2025-10581

HIGH · 7.8 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 5.1.140.9262 or later.
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
A potential DLL hijacking vulnerability was discovered in the Lenovo PC Manager during an internal security assessment that could allow a local authenticated user to execute code with elevated privileges.

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 · moderate confidence

A DLL hijacking vulnerability in Lenovo PC Manager allows a local authenticated user to place a malicious DLL in a location where the application loads DLLs from, enabling code execution with elevated privileges. The vulnerability stems from insecure DLL search path usage during the application's runtime.

MitigationApply the vendor patch from Lenovo when available. Until then, restrict write access to directories in the application’s DLL search path and monitor for unauthorized DLL placement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PcmanagerApplication
Affected:< 5.1.140.9262

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 installed Lenovo PC Manager version
    Open Lenovo PC Manager, go to Settings or About section to view the version number. Alternatively, right-click the main executable (typically lenovo_pc_manager.exe or similar) in the installation folder, select Properties, and check the Details tab for the File Version.
    Affected if Version is lower than 5.1.140.9262 (the first fixed version)
  2. Locate Lenovo PC Manager installation directory
    Navigate to Program Files or Program Files (x86) and look for a Lenovo or PCManager folder. You can also right-click the desktop shortcut, select Open file location, to find the installation path.
    Affected if Application is installed and the version check in Step 1 shows a vulnerable version
  3. Inspect application directory for unexpected DLL files
    Open the Lenovo PC Manager installation folder and examine all .dll files present. Look for DLLs with unusual names, recent modification dates, or that do not belong to the standard application.
    Affected if Unknown or suspicious DLL files are present in the application directory that could be maliciously placed
  4. Verify write permissions on DLL search path directories
    Right-click the Lenovo PC Manager installation folder, select Properties, go to the Security tab, and check which users have Write or Modify permissions. Focus on directories where the application loads DLLs from.
    Affected if Non-privileged users or groups have Write permissions to directories in the application DLL search path, allowing them to place malicious DLLs

You are affected if Lenovo PC Manager is installed with a version lower than 5.1.140.9262 and any directory in its DLL search path is writable by non-privileged users.

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
Upgrade available Upgrade to 5.1.140.9262 or later
Fixed in 5.1.140.9262
Interim mitigation

Apply the vendor patch from Lenovo when available. Until then, restrict write access to directories in the application’s DLL search path and monitor for unauthorized DLL placement.

Recommended fix High confidence

5.1.140.9262 or later

  1. Download Lenovo PC Manager version 5.1.140.9262 or later from the official Lenovo support site
  2. Ensure you download from a trusted Lenovo domain (support.lenovo.com or iknow.lenovo.com.cn)
  3. Close any running instances of Lenovo PC Manager
  4. Install the updated version of Lenovo PC Manager
  5. Restart your computer to ensure the updated DLLs are properly loaded
  6. Verify the installed version is 5.1.140.9262 or higher

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

Fix this in Pcmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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