# CVE-2025-50777: Auth bypass in n/a

> Local attackers can bypass access controls to gain root shell access on AZIOT cameras, exposing plaintext Wi-Fi and ONVIF credentials.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-m2c5-wgww-2xf2

## What is CVE-2025-50777?

CVE-2025-50777 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The firmware of the AZIOT 2MP Full HD Smart Wi-Fi CCTV Home Security Camera (version V1.00.02) contains an Incorrect Access Control vulnerability that allows local attackers to gain root shell access. Once accessed, the device exposes critical data including Wi-Fi credentials and ONVIF service credentials stored in plaintext, enabling further compromise of the network and connected systems.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Aziot 2mp Full Hd Smart Wi-Fi Cctv Home Security Camera Firmware.

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

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

## Is CVE-2025-50777 being exploited?

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

Public exploit code:

- CVE-2025-50777: Root Access and Plaintext Credential Exposure in AZIOT Smart CCTV (github_poc): https://github.com/veereshgadige/aziot-cctv-cve-2025-50777

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50777 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50777 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-50777/ (Markdown: https://insights.sbomify.com/CVE-2025-50777/index.md)
```

## Sources

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

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