dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-60855

MEDIUM · 5.1 CVSS v3.1 Published 2025-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
53/100
Remediation priority · Moderate
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
Reolink Video Doorbell WiFi DB_566128M5MP_W performs insufficient validation of firmware update signatures. This allows attackers to load malicious firmware images, resulting in arbitrary code execution with root privileges. NOTE: this is disputed by the Supplier because the integrity of updates is instead assured via a "private encryption algorithm" and other "tamper-proof verification."

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 Reolink Video Doorbell WiFi DB_566128M5MP_W fails to properly validate cryptographic signatures on firmware updates before installation. This allows an attacker who can intercept or supply malicious firmware to the device to bypass the update mechanism, causing the device to install and execute arbitrary code with root privileges.

MitigationSince the vendor disputes the vulnerability and a firmware patch may not be available, implement compensating controls: isolate the device on a restricted network segment/VLAN, disable external firmware update exposure, and monitor for anomalous update traffic. Consider device replacement if no vendor patch emerges.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/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. Confirm device model
    Identify the exact model of the Reolink doorbell device in your environment - verify it is the DB_566128M5MP_W variant of the Reolink Video Doorbell WiFi
    Affected if The device is a Reolink Video Doorbell WiFi DB_566128M5MP_W model
  2. Check current firmware version
    Access the device web interface or mobile app and locate the firmware version information, typically found under Settings, Device Info, or About sections
    Affected if The installed firmware version predates any available patched release addressing signature validation
  3. Verify firmware update mechanism exposure
    Determine if the device firmware update interface is accessible over the network - check if the device is reachable on its administrative ports and if firmware update functionality is enabled
    Affected if The device firmware update mechanism is network-accessible and not restricted to local-only updates
  4. Assess network segmentation
    Examine the network placement of the device - verify whether it resides on a dedicated VLAN or isolated network segment separate from untrusted devices and the internet
    Affected if The device is on the same network segment as untrusted devices or directly exposed to the internet without isolation
  5. Monitor for unexpected update traffic
    Inspect network traffic logs or use packet capture to identify any firmware update requests or responses, noting their source, destination, and whether they occur at unexpected times
    Affected if Firmware update traffic is detected from unexpected sources or during unusual times indicating potential interception

You are affected if you are using a Reolink Video Doorbell WiFi DB_566128M5MP_W where the firmware update mechanism is network-accessible and the device is not isolated on a restricted network segment.

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

Since the vendor disputes the vulnerability and a firmware patch may not be available, implement compensating controls: isolate the device on a restricted network segment/VLAN, disable external firmware update exposure, and monitor for anomalous update traffic. Consider device replacement if no vendor patch emerges.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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