Incorrect AuthorizationWeakness · CWE-863

CVE-2025-14305

HIGH · 7.8 CVSS v3.1 Published 2025-12-17
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
ListCheck.exe developed by Acer has a Local Privilege Escalation vulnerability. Authenticated local attackers can replace ListCheck.exe with a malicious executable of the same name, which will be executed by the system and result in privilege escalation.

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

ListCheck.exe developed by Acer contains a local privilege escalation vulnerability where an authenticated local attacker can replace the legitimate ListCheck.exe binary with a malicious executable of the same name. Since the system executes ListCheck.exe with elevated privileges, the attacker gains those privileges when the replaced binary is run.

MitigationReplace or remove the vulnerable ListCheck.exe binary and investigate what process or service executes it and with what privileges. Implement code signing verification or ensure the executable is stored in a secure location with appropriate access controls.

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. Locate ListCheck.exe on the system
    Search for the file ListCheck.exe on all drives using commands like 'dir /s /b C:\ListCheck.exe' or use Windows Search. Check common Acer installation directories such as C:\Program Files\Acer or C:\ProgramData\Acer.
    Affected if ListCheck.exe file is found on the system
  2. Identify the parent process that launches ListCheck.exe
    Use Sysinternals Process Explorer or Process Monitor to identify which process or service invokes ListCheck.exe. Run 'wmic process where "name='ListCheck.exe'" get parentprocessid' if the process is currently running.
    Affected if A process or service executes ListCheck.exe automatically or on a schedule
  3. Verify if ListCheck.exe runs with elevated privileges
    When ListCheck.exe is launched, check its token elevation status using Process Explorer or by running 'tasklist /V' to view the privilege level. Look for HIGH or SYSTEM integrity level.
    Affected if ListCheck.exe executes with administrative or SYSTEM privileges
  4. Check file permissions on ListCheck.exe
    Right-click the ListCheck.exe file, go to Properties > Security, or run 'icacls ListCheck.exe' from an elevated command prompt to review who has Write or Write-ACL permissions on the file.
    Affected if Non-admin users or the current user has Write permission to the ListCheck.exe file or its containing folder
  5. Determine if the file is in a user-writable location
    Examine the full path of ListCheck.exe. If it resides in folders like %TEMP%, %APPDATA%, or other user-writable directories rather than protected system folders, the replacement attack is feasible.
    Affected if ListCheck.exe is located in a directory accessible to standard users or low-privileged accounts

A user is affected if ListCheck.exe exists on their system, runs with elevated privileges, and resides in a location where an authenticated attacker could replace the binary with a malicious version.

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

Replace or remove the vulnerable ListCheck.exe binary and investigate what process or service executes it and with what privileges. Implement code signing verification or ensure the executable is stored in a secure location with appropriate access controls.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-14305 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