Thinkplus Fu100 FirmwareOperating system · Lenovo

CVE-2025-13455

HIGH · 7.8 CVSS v3.1 Published 2026-01-14
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
A vulnerability was reported in ThinkPlus configuration software that could allow a local authenticated user to bypass ThinkPlus device authentication and enroll an untrusted fingerprint.

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

ThinkPlus configuration software contains a local authentication bypass vulnerability allowing an authenticated low-privilege user to bypass device authentication controls and enroll an untrusted fingerprint. This is a local attack requiring authenticated access, where the enrollment validation logic fails to properly verify the user's identity before accepting fingerprint data.

MitigationApply vendor-supplied patch for ThinkPlus configuration software when available; until then, restrict physical and console access to systems running this software and monitor for unauthorized fingerprint enrollment events.

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
Thinkplus Fu100 FirmwareOperating system
Affected:all versions
Thinkplus Fu200 FirmwareOperating system
Affected:all versions
Thinkplus Tu800 FirmwareOperating system
Affected:all versions
Thinkplus Tsd303 FirmwareOperating system
Affected:all versions

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. Identify ThinkPlus software installation
    Search for ThinkPlus configuration software on the system - look for application files, services, or drivers named ThinkPlus, Fu100, Fu200, Tu800, or Tsd303
    Affected if ThinkPlus configuration software is installed on the system
  2. Identify ThinkPlus device model
    Check for connected USB or attached ThinkPlus fingerprint devices - Fu100, Fu200, Tu800, or Tsd303 models
    Affected if Any of the affected device models (Fu100, Fu200, Tu800, Tsd303) are connected or installed
  3. Check for existing fingerprint enrollments
    Review the ThinkPlus configuration software or system for any enrolled fingerprints - look for enrollment records, user-fingerprint mappings, or fingerprint templates stored on the system
    Affected if Fingerprints have been enrolled through the ThinkPlus software
  4. Review enrollment audit logs
    Examine system event logs, application logs, or security logs for fingerprint enrollment events performed by users - look for enrollment timestamps, user accounts, and enrollment success/failure records
    Affected if Fingerprint enrollment events exist in logs, especially from low-privilege user accounts
  5. Verify user access patterns
    Check which user accounts have access to the ThinkPlus configuration software and fingerprint enrollment features - review permissions, user groups, and authentication contexts
    Affected if Low-privilege or standard user accounts have access to fingerprint enrollment functionality

If ThinkPlus configuration software with any of the affected device models (Fu100, Fu200, Tu800, Tsd303) is present and fingerprint enrollment is accessible to authenticated users, the environment is affected by this vulnerability.

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 vendor-supplied patch for ThinkPlus configuration software when available; until then, restrict physical and console access to systems running this software and monitor for unauthorized fingerprint enrollment events.

Fix this in Thinkplus Fu100 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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