CVE-2025-60858
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 · uneditedReolink Video Doorbell Wi-Fi DB_566128M5MP_W stores and transmits DDNS credentials in plaintext within its configuration and update scripts, allowing attackers to intercept or extract sensitive information.
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 confidenceThe Reolink Video Doorbell Wi-Fi DB_566128M5MP_W stores DDNS credentials in plaintext within its configuration files and update scripts, and also transmits these credentials without encryption. An attacker with network interception capability or filesystem access can extract the plaintext credentials.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelIdentify the Reolink Video Doorbell Wi-Fi model DB_566128M5MP_W on your network or physically on the device labelAffected if The device is a Reolink Video Doorbell Wi-Fi DB_566128M5MP_W model
-
Check if DDNS is configuredAccess the device web interface or mobile app and navigate to DDNS settings to see if a DDNS service is enabledAffected if DDNS is configured and enabled on the device
-
Inspect configuration files for plaintext credentialsIf you have filesystem access (e.g., via SSH, Telnet, or SD card), examine configuration files in /etc or /mnt for files containing DDNS provider credentials in plaintextAffected if Configuration files contain DDNS username/password in plaintext
-
Examine update scripts for credentialsIf you have filesystem access, inspect shell scripts in /scripts or similar directories used for firmware updates for hardcoded DDNS credentialsAffected if Update scripts contain plaintext DDNS credentials
-
Monitor network traffic for unencrypted transmissionUse a network sniffer on the same network segment to capture traffic between the device and the DDNS provider server, observing if credentials are sent in cleartext HTTPAffected if DDNS credentials are transmitted without TLS encryption
A user is affected if they use a Reolink Video Doorbell Wi-Fi DB_566128M5MP_W with DDNS configured, and plaintext DDNS credentials are present in config files or transmitted unencrypted on the network.
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 dataAwait vendor firmware patch; in the interim, change DDNS credentials, isolate device on dedicated network segment, and monitor for unauthorized access using the compromised credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60858 — 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-60858 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