CVE-2025-55627
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 · uneditedInsufficient privilege verification in Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell with Chime - firmware v3.0.0.4662_2503122283 allows authenticated attackers to create accounts with elevated privileges.
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 confidenceInsufficient privilege verification in the Reolink Smart 2K+ Doorbell firmware v3.0.0.4662_2503122283 allows any authenticated user to create new user accounts with elevated privileges, enabling vertical privilege escalation within the device's user management system.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify device modelAccess the device settings via Reolink app or web interface and verify the device is a Reolink Smart 2K+ Doorbell. Check the device info or about section.Affected if Device model is Reolink Smart 2K+ Doorbell
-
Check firmware versionNavigate to device settings, look for firmware version information. The affected version is v3.0.0.4662_2503122283. Compare your installed version against this.Affected if Firmware version is v3.0.0.4662_2503122283 or lower
-
Verify user account listAccess the user management or account settings panel on the device. List all configured user accounts.Affected if Multiple accounts exist beyond the initial admin account, or unexpected elevated accounts are present
-
Review account creation logsCheck system logs or event history for user account creation events, especially those created by non-admin users.Affected if Logs show user accounts created by users who should not have administrative privileges
-
Audit privilege assignmentsIn user management, verify the privilege level assigned to each account. The vulnerability allows creation of elevated privilege accounts.Affected if Accounts with elevated privileges exist that were not created by the primary administrator
Device is affected if it is a Reolink Smart 2K+ Doorbell running firmware v3.0.0.4662_2503122283 and any unauthorized or additional user accounts with elevated privileges are present.
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-supplied firmware update when available; until then, limit device administrative access to trusted users only and monitor for unauthorized account creation.
- Consultation6.0 h
- Implementation3.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 $4,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55627 — 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-55627 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