dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-7723

HIGH · 8.5 CVSS v4.0 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in TP-Link VIGI NVR devices (models VIGI NVR1104H-4P V1 and VIGI NVR2016H-16MP V2). An authenticated attacker can execute arbitrary system commands on the device by injecting OS commands through vulnerable input fields, potentially leading to full device compromise.

MitigationUpdate VIGI NVR firmware to version 1.1.5 Build 250518 or later for V1, and 1.3.1 Build 250407 or later for V2. Restrict administrative access to trusted networks and enforce strong authentication credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the TP-Link VIGI NVR web management interface and navigate to System > System Info to confirm the exact model number (VIGI NVR1104H-4P V1 or VIGI NVR2016H-16MP V2).
    Affected if The device is a VIGI NVR1104H-4P V1 or VIGI NVR2016H-16MP V2 model.
  2. Check the installed firmware version
    In the web interface, go to System > System Info and locate the Firmware Version field. Note both the version number and build date.
    Affected if For V1 models: version is below 1.1.5 or build date is before 250518. For V2 models: version is below 1.3.1 or build date is before 250407.
  3. Verify remote management exposure
    Check the network configuration to determine if the NVR web interface (typically ports 80/443 or configured HTTP/HTTPS port) is accessible from external/untrusted networks rather than only from an isolated management VLAN.
    Affected if The administrative web interface is reachable from untrusted network segments or the public internet.
  4. Confirm authentication is required
    Attempt to access the web interface without credentials or verify that login is enforced and session timeouts are configured.
    Affected if The interface is accessible without authentication or uses default/weak administrative credentials.

The device is affected if it is a VIGI NVR1104H-4P V1 or VIGI NVR2016H-16MP V2 running firmware below version 1.1.5 (V1) or 1.3.1 (V2) AND the management interface is accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update VIGI NVR firmware to version 1.1.5 Build 250518 or later for V1, and 1.3.1 Build 250407 or later for V2. Restrict administrative access to trusted networks and enforce strong authentication credentials.

Recommended fix High confidence

VIGI NVR1104H-4P V1: upgrade to 1.1.5 Build 250518 or later; VIGI NVR2016H-16MP V2: upgrade to 1.3.1 Build 250407 or later

  1. 1. Identify the exact model of TP-Link VIGI NVR device in your environment (NVR1104H-4P V1 or NVR2016H-16MP V2).
  2. 2. Access the device management interface through the web GUI or local console.
  3. 3. Navigate to the firmware update section in the device settings.
  4. 4. Download the firmware update from the official TP-Link support website (www.tp-link.com) ensuring you obtain the correct build for your model: For NVR1104H-4P V1, use version 1.1.5 Build 250518 or later; For NVR2016H-16MP V2, use version 1.3.1 Build 250407 or later.
  5. 5. Upload the firmware file to the device and initiate the upgrade process.
  6. 6. Wait for the firmware update to complete and the device to reboot.
  7. 7. Verify the firmware version has been updated successfully and test that normal NVR functionality is operational.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7723 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data