# CVE-2025-6531: SIFUSM/MZZYG BD S1 RTSP Live Video Stream Endpoint access control

> An attacker on the local network can access the RTSP live video stream without proper authorization, exposing sensitive video data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-76q9-9h4j-5fwq

## What is CVE-2025-6531?

CVE-2025-6531 is a medium-severity missing authorization vulnerability in MZZYG BD S1, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in SIFUSM/MZZYG BD S1 up to 20250611. It has been declared as problematic. This vulnerability affects unknown code of the component RTSP Live Video Stream Endpoint. The manipulation leads to improper access controls. Access to the local network is required for this attack to succeed. The exploit has been disclosed to the public and may be used. This dashcam is distributed by multiple resellers and different names.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-6531 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6531 is a medium-severity missing authorization vulnerability in MZZYG BD S1, published on 23 Jun 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-6531 exists.

Affected product: MZZYG BD S1. 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-6531/ (Markdown: https://insights.sbomify.com/CVE-2025-6531/index.md)
```

## Sources

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

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