dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-13155

HIGH · 7.8 CVSS v3.1 Published 2025-12-10
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
An improper permissions vulnerability was reported in Lenovo Baiying Client 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

Lenovo Baiying Client contains an improper permissions vulnerability where the application fails to enforce appropriate access controls on sensitive resources, allowing an authenticated local user to manipulate files or execution contexts to gain elevated (administrator/SYSTEM) privileges. This is a local privilege escalation vector requiring prior local access.

MitigationApply least-privilege principles to all executable paths, service configurations, and data directories within Lenovo Baiying Client; verify correct ACLs restrict write access for non-admin users to privileged locations.

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 Lenovo Baiying Client is installed
    Look for the application in standard installation directories (C:\Program Files\Lenovo\ or C:\Program Files (x86)\Lenovo\) or check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry containing 'Baiying' or 'Lenovo' and client-related naming
    Affected if The application is found installed on the system
  2. Identify installed version
    Check the version value in the Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Lenovo\Baiying\ or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lenovo\Baiying\ (adjust path based on actual install location found in step 1), or right-click the main executable and select Properties > Details to view File Version
    Affected if A version number is retrieved and can be compared to any affected version range when known
  3. Examine file permissions on application executable directory
    Right-click the main application folder (e.g., C:\Program Files\Lenovo\Baiying\) > Properties > Security tab. Check if Users or Authenticated Users have Write or Modify permissions. Alternatively, run: icacls "C:\Program Files\Lenovo\Baiying" to list all ACLs
    Affected if Non-admin users (such as standard Users group) have Write, Modify, or Full Control permissions to the application directory or its executables
  4. Inspect service configuration if running as a Windows service
    Open Services (services.msc), locate any Lenovo Baiying service, right-click > Properties. Note the Log On account (often LocalSystem or a specific service account). Then run: sc qc <service_name> to query the binary path
    Affected if The service runs with elevated privileges (LocalSystem) AND non-admin users have Write permissions to the service executable or its configuration files
  5. Check for weak ACLs on program data or configuration directories
    Examine permissions on directories like C:\ProgramData\Lenovo\Baiying\ or the application's config folder within the install directory. Run: icacls "C:\ProgramData\Lenovo\Baiying" and verify if standard users can modify files
    Affected if Users group or Authenticated Users have Write access to configuration files, XML files, or executable scripts in these directories
  6. Look for modifiable execution contexts
    Search for any .exe, .bat, .cmd, or .dll files under the application folder that are writable by non-admin users. Run: icacls "C:\Program Files\Lenovo\Baiying\*" | findstr /i "(F|M|W)" to list files with write access, then cross-reference with user group permissions
    Affected if Executable files or scripts within the application directory are writable by standard users or can be replaced by them

A user is affected if Lenovo Baiying Client is installed AND non-privileged users have Write or Modify permissions to application directories, executables, services, or configuration files that should be restricted to administrators only.

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

Apply least-privilege principles to all executable paths, service configurations, and data directories within Lenovo Baiying Client; verify correct ACLs restrict write access for non-admin users to privileged locations.

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