dbcve.org
PcmanagerApplication · Lenovo

CVE-2025-2501

HIGH · 7.8 CVSS v3.1 Published 2025-05-30
Fix available
A fix is available. Upgrade to 5.1.110.5082 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
An untrusted search path vulnerability was reported in Lenovo PC Manager that could allow a local attacker to elevate 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

Lenovo PC Manager contains an untrusted search path vulnerability where the application loads DLLs or executables from locations that a local attacker can control. A local unprivileged attacker can place a malicious DLL in a search path location used by the application, causing it to execute with elevated privileges when Lenovo PC Manager runs.

MitigationApply vendor patches from Lenovo when available. As a temporary workaround, ensure the directory where Lenovo PC Manager is installed and system PATH directories are not writable by unprivileged users.

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.110.5082

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. Find Lenovo PC Manager installation directory
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode} or check C:\Program Files\Lenovo\PCManager and C:\Program Files (x86)\Lenovo\PCManager folders
    Affected if The application is installed but the folder does not exist or cannot be located
  2. Determine installed version of Lenovo PC Manager
    Right-click on PCManager.exe in the installation folder, select Properties, then view the Details tab to see the File Version. Alternatively, run 'wmic product get name,version' or check the uninstall registry entry for the version number
    Affected if The version number displayed is less than 5.1.110.5082
  3. Check write permissions on the Lenovo PC Manager installation folder
    Right-click the installation folder (e.g., C:\Program Files\Lenovo\PCManager), select Properties, go to the Security tab, and check if Users or Authenticated Users have Write or Modify permissions
    Affected if Unprivileged users (such as standard Users group) have Write or Modify permissions to the installation directory
  4. Check write permissions on system PATH directories
    Open System Properties > Advanced > Environment Variables, review each directory listed in the System PATH variable, and check folder permissions for unprivileged write access
    Affected if Any directory in the system PATH is writable by unprivileged users

You are affected if Lenovo PC Manager version is below 5.1.110.5082 AND unprivileged users can write to either the application installation directory or any directory in the system PATH.

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.110.5082 or later
Fixed in 5.1.110.5082
Interim mitigation

Apply vendor patches from Lenovo when available. As a temporary workaround, ensure the directory where Lenovo PC Manager is installed and system PATH directories are not writable by unprivileged users.

Recommended fix High confidence

5.1.110.5082 or later

  1. Download the latest version of Lenovo PC Manager from the official Lenovo support website or through the application's built-in update mechanism
  2. Ensure you are downloading from official Lenovo sources (support.lenovo.com or iknow.lenovo.com.cn) to avoid counterfeit software
  3. Run the installer with administrator privileges
  4. Restart your computer after the update completes to ensure all components are properly initialized
  5. Verify the installed version is 5.1.110.5082 or later by opening PC Manager and checking About or Settings

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

Fix this in Pcmanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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