dbcve.org
PcmanagerApplication · Lenovo

CVE-2025-2502

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 improper default permissions 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 improper default permissions that allow a local unprivileged attacker to modify files or execute code with elevated privileges. This is a local privilege escalation vulnerability where the application creates or modifies resources with overly permissive access controls.

MitigationApply vendor patch when released, or remove/disable Lenovo PC Manager if unnecessary. If the software is required, implement compensating controls such as restricting user access to the application directory and monitoring for unauthorized privilege escalation attempts.

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. Verify Lenovo PC Manager is installed
    Check for Lenovo PC Manager in the system registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the application in Program Files
    Affected if The software is found installed on the system
  2. Determine installed version
    Open the application or check its properties to find the version number. Compare against the fixed version 5.1.110.5082
    Affected if The installed version is lower than 5.1.110.5082 (e.g., 5.1.100.0000, 5.0.x.x, etc.)
  3. Inspect application directory permissions
    Right-click the Lenovo PC Manager installation folder (typically in Program Files or Program Files (x86)), go to Properties > Security, and examine the permissions granted to Users or standard user accounts
    Affected if Users or standard non-admin accounts have Write or Modify permissions to the application directory or its executable files
  4. Check for overly permissive service or process
    Open Services, find any Lenovo PC Manager-related service, right-click and view Properties. Also check the Task Manager for running Lenovo processes and their execution level
    Affected if The service runs under a privileged account (like SYSTEM or LocalSystem) while the application files are writable by unprivileged users

The system is affected if Lenovo PC Manager is installed with a version lower than 5.1.110.5082 AND the application directory or files have permissions allowing standard users to modify executable files or configurations.

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 patch when released, or remove/disable Lenovo PC Manager if unnecessary. If the software is required, implement compensating controls such as restricting user access to the application directory and monitoring for unauthorized privilege escalation attempts.

Recommended fix High confidence

Lenovo PC Manager 5.1.110.5082 or later

  1. Open Windows Settings > Apps > Apps & features (or Programs and Features in Control Panel)
  2. Locate Lenovo PC Manager in the installed programs list
  3. Note the current version number for verification
  4. Visit the official Lenovo support page at iknow.lenovo.com.cn or Lenovo Vantage/PC Support to download the latest Lenovo PC Manager
  5. Download the installer for version 5.1.110.5082 or later
  6. Run the installer as Administrator to apply the update
  7. Restart the computer if prompted
  8. Verify the installed version is 5.1.110.5082 or higher

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

Fix this in Pcmanager 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 the upgrade done

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-2502 — 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-2502 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