dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2025-25650

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 issue in the storage of NFC card data in Dorset DG 201 Digital Lock H5_433WBSK_v2.2_220605 allows attackers to produce cloned NFC cards to bypass authentication.

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

The Dorset DG 201 Digital Lock H5_433WBSK_v2.2_220605 stores NFC card data insecurely, allowing attackers to extract the stored card data and create cloned NFC cards that bypass the lock's authentication mechanism.

MitigationApply vendor firmware update if available; if no update exists, implement supplementary physical security measures and consider transitioning to more secure card authentication methods.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 the lock model in your environment
    Physically inspect or inventory the digital lock to confirm it is a Dorset DG 201 Digital Lock with model identifier H5_433WBSK_v2.2_220605
    Affected if The lock model matches Dorset DG 201 or H5_433WBSK_v2.2_220605
  2. Check the installed firmware version
    Access the lock's administrative interface or configuration menu to view the firmware version; compare against the affected version H5_433WBSK_v2.2_220605
    Affected if The firmware version is H5_433WBSK_v2.2_220605 or earlier
  3. Confirm NFC card enrollment is enabled
    Verify that the lock is configured to use NFC card authentication; check if any NFC cards have been registered to the lock system
    Affected if NFC card authentication is active and cards are registered to the lock
  4. Determine if card data storage is accessible
    Examine the lock's data storage mechanism or connected system to determine if NFC card credentials are stored in an insecure or unencrypted manner
    Affected if NFC card data is stored without encryption or with easily extractable credentials

You are affected if you have a Dorset DG 201 Digital Lock (H5_433WBSK_v2.2_220605) with NFC card authentication enabled and the firmware matches the affected version, as the card data can be extracted and cloned.

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 firmware update if available; if no update exists, implement supplementary physical security measures and consider transitioning to more secure card authentication methods.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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