# CVE-2021-47707: COMMAX CVD-Axx DVR Weak Default Credentials Stream Disclosure

> Attackers can access the web control panel and RTSP streams using weak default administrative credentials, compromising video surveillance data.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-q6gq-vxg6-9m9p

## What is CVE-2021-47707?

CVE-2021-47707 is a critical vulnerability in COMMAX CVD-Axx DVR, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

COMMAX CVD-Axx DVR 5.1.4 contains weak default administrative credentials that allow remote password attacks and disclose RTSP stream. Attackers can exploit this by sending a POST request with the 'passkey' parameter set to '1234', allowing them to access the web control panel.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2021-47707?


## How do I fix CVE-2021-47707?

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

## Is CVE-2021-47707 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47707 and fix it if it is affected.

What it is: CVE-2021-47707 is a critical vulnerability in COMMAX CVD-Axx DVR, published on 9 Dec 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-2021-47707 exists.

Affected product: COMMAX CVD-Axx DVR. 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-2021-47707/ (Markdown: https://insights.sbomify.com/CVE-2021-47707/index.md)
```

## Sources

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

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