dbcve.org
PcmanagerApplication · Lenovo

CVE-2025-8098

HIGH · 7.8 CVSS v3.1 Published 2025-08-18
Fix available
A fix is available. Upgrade to 5.1.120.7041 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 permission vulnerability was reported in Lenovo PC Manager that could allow a local attacker to escalate 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 improper permission vulnerability that allows a local attacker to exploit misconfigured file system or registry permissions to elevate privileges from standard user to administrator or SYSTEM. The vulnerability is exploitable locally by an attacker with physical access or a low-privilege user account on the target system.

MitigationApply the vendor patch from Lenovo when available. As a temporary workaround, consider disabling or removing Lenovo PC Manager if not required, or restrict user access to the affected service/files until the patch can be applied.

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

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 the presence of Lenovo PC Manager in the system: Look in C:\Program Files\Lenovo\PCManager or C:\Program Files (x86)\Lenovo\PCManager, or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Lenovo PC Manager'
    Affected if The software is found installed on the system
  2. Determine installed version of Lenovo PC Manager
    Open Programs and Features in Control Panel, find 'Lenovo PC Manager', and note the version number displayed, or query the registry key under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the DisplayVersion value
    Affected if The version shown is lower than 5.1.120.7041
  3. Inspect file system permissions on PC Manager directories
    Right-click the Lenovo PC Manager installation folder (typically in Program Files), select Properties, go to the Security tab, and examine which users or groups have Write or Full Control permissions. Use 'icacls' command or Security tab to identify non-admin users with elevated permissions
    Affected if Standard users or low-privilege accounts have Write or Full Control permissions to PC Manager executables or configuration folders
  4. Inspect registry permissions on PC Manager keys
    Open regedit, navigate to HKLM\SOFTWARE\Lenovo\PCManager or related keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, right-click the key, select Permissions, and verify which users have Write or Full Control access
    Affected if Standard users or low-privilege accounts have Write or Full Control permissions to PC Manager registry keys that control service execution or startup

A system is affected if Lenovo PC Manager version is below 5.1.120.7041 AND the installation directory or registry keys have misconfigured permissions allowing standard users to modify executable files or service 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.120.7041 or later
Fixed in 5.1.120.7041
Interim mitigation

Apply the vendor patch from Lenovo when available. As a temporary workaround, consider disabling or removing Lenovo PC Manager if not required, or restrict user access to the affected service/files until the patch can be applied.

Recommended fix Moderate confidence

5.1.120.7041 or later

  1. 1. Open Lenovo PC Manager on the affected system
  2. 2. Navigate to the settings or about section within the application
  3. 3. Check the current version number displayed
  4. 4. If the version is below 5.1.120.7041, look for an update option (check for updates or settings > update)
  5. 5. Download and install the latest available version from the official Lenovo update server
  6. 6. Alternatively, download the updated installer directly from Lenovo's official support website (support.lenovo.com)
  7. 7. Restart the system after installation to ensure all services run with corrected permissions
  8. 8. Verify the installed version is 5.1.120.7041 or higher
Caveat Standard minor version upgrade; no major configuration changes expected

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

Fix this in Pcmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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