CVE-2025-55637
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 Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime - firmware v3.0.0.4662_2503122283 was discovered to contain a command injection vulnerability via the setddns_pip_system() function.
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 confidenceA command injection vulnerability exists in the setddns_pip_system() function of Reolink Smart 2K+ Wi-Fi Video Doorbell firmware v3.0.0.4662_2503122283, allowing remote attackers to execute arbitrary OS commands via unsanitized input.
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= 3.0.0.4662_2503122283CVSS 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.
-
Identify the device modelLocate the Reolink Smart 2K+ Wi-Fi Video Doorbell device in your network inventory or physically inspect the device labeling. Confirm it is the specific model: Reolink Smart 2k+ Plug In WiFi Video Doorbell With Chime.Affected if The device is not a Reolink Smart 2K+ Wi-Fi Video Doorbell model.
-
Determine the installed firmware versionAccess the Reolink app or the device web interface. Navigate to Settings > Device Info > Firmware Version. Alternatively, check via the Reolink Client software under device properties.Affected if The installed firmware version is exactly 3.0.0.4662_2503122283.
-
Locate the DDNS or PIP configuration settingsIn the Reolink app or web interface, look for DDNS settings (often under Network or Advanced settings) or PIP (Picture-in-Picture) settings. The vulnerable function setddns_pip_system() relates to these features.Affected if DDNS or PIP configuration options are present and accessible in the device interface.
-
Check if DDNS service is enabledIn the device settings under DDNS configuration, verify whether any DDNS provider is configured and enabled. The command injection occurs through the setddns_pip_system() function.Affected if DDNS is enabled with any provider configuration on the device.
Your environment is affected only if you have a Reolink Smart 2K+ Wi-Fi Video Doorbell With Chime running firmware version 3.0.0.4662_2503122283 with DDNS or PIP features accessible and enabled.
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 update when available; until then, isolate the device on a restricted network segment and disable unnecessary external access to reduce attack surface.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55637 — 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-55637 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