CVE-2025-14346
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 · uneditedWHILL Model C2 Electric Wheelchairs and Model F Power Chairs do not enforce authentication for Bluetooth connections. An attacker within range can pair with the device and issue movement commands, override speed restrictions, and manipulate configuration profiles without any credentials or user interaction.
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 confidenceWHILL Model C2 and Model F wheelchairs lack authentication enforcement for Bluetooth connections, allowing any nearby attacker to pair and send commands without credentials. An attacker can issue movement commands, override speed restrictions, and modify configuration profiles with no user interaction required.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm wheelchair modelLocate the model identifier on the wheelchair frame, joystick controller, or in the product documentation. Verify if the device is a WHILL Model C2 or Model F.Affected if If the wheelchair is a WHILL Model C2 or Model F, it falls within the affected product range for this CVE.
-
Check Bluetooth statusAccess the wheelchair control panel or companion mobile application. Determine whether Bluetooth wireless functionality is currently enabled.Affected if If Bluetooth is turned on and the device is a WHILL Model C2 or Model F, the vulnerability is present and exploitable.
-
Verify pairing accessibilityCheck if the wheelchair is set to discoverable or pairable mode, which allows nearby Bluetooth devices to initiate connections without credentials.Affected if If the device accepts pairing requests without requiring authentication, it is affected by the lack of authentication enforcement.
-
Inspect paired devices listUsing the WHILL mobile application or device settings, review the list of currently paired Bluetooth devices for any unknown or unrecognized connections.Affected if If unauthorized paired devices are present, the wheelchair has likely been compromised through this vulnerability.
A user is affected if they own a WHILL Model C2 or Model F wheelchair with Bluetooth enabled, as the device allows unauthenticated Bluetooth pairing and command injection.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware updates when released; until then, reduce Bluetooth exposure by using devices in controlled environments and monitor for unauthorized pairing attempts.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14346 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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