# CVE-2025-55627: Privilege escalation in n/a

> Authenticated attackers can create accounts with elevated privileges due to insufficient privilege verification in the Reolink Smart 2K+ Plug-in Wi-Fi Video Doorbell firmware.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2025
- **Updated:** 22 Aug 2025
- **Also known as:** GHSA-hp78-rj98-c429

## What is CVE-2025-55627?

CVE-2025-55627 is a medium-severity vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient 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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-55627?


## How do I fix CVE-2025-55627?

No fix has been published for CVE-2025-55627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55627 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55627 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55627 and fix it if it is affected.

What it is: CVE-2025-55627 is a medium-severity vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55627 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55627/ (Markdown: https://insights.sbomify.com/CVE-2025-55627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55627
- OSV: https://osv.dev/vulnerability/CVE-2025-55627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55627/
Summaries are generated and may contain mistakes; the official description above is the record.