# CVE-2025-7723: Authenticated command injection on VIGI NVR1104H-4P V1 and VIGI NVR2016H-16MP V2

> Authenticated attackers can execute arbitrary commands on TP-Link VIGI NVR devices via a command injection vulnerability.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-h2qv-8rr4-vmcr

## What is CVE-2025-7723?

CVE-2025-7723 is a high-severity command injection vulnerability in TP-Link Systems Inc. VIGI NVR1104H-4P V1, published on 22 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A command injection vulnerability exists that can be exploited after authentication in VIGI NVR1104H-4P V1 and VIGI NVR2016H-16MP V2.This issue affects VIGI NVR1104H-4P V1: before 1.1.5 Build 250518; VIGI NVR2016H-16MP V2: before 1.3.1 Build 250407.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-7723 being exploited?

There is no known exploitation of CVE-2025-7723 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7723 is a high-severity command injection vulnerability in TP-Link Systems Inc. VIGI NVR1104H-4P V1, published on 22 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7723 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. VIGI NVR1104H-4P V1. 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-7723/ (Markdown: https://insights.sbomify.com/CVE-2025-7723/index.md)
```

## Sources

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

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