dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-7724

HIGH · 8.7 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 →
92/100
Remediation priority · Urgent
No privileges 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
An unauthenticated OS command injection vulnerability exists 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

Unauthenticated OS command injection vulnerability in TP-Link VIGI NVR web interface allows remote attackers to execute arbitrary OS commands by injecting malicious input into vulnerable parameters. The flaw affects VIGI NVR1104H-4P V1 before version 1.1.5 Build 250518 and VIGI NVR2016H-16MP V2 before version 1.3.1 Build 250407.

MitigationApply the vendor-supplied firmware updates to remediate: update VIGI NVR1104H-4P V1 to 1.1.5 Build 250518 or later, and VIGI NVR2016H-16MP V2 to 1.3.1 Build 250407 or later.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/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 NVR web interface and navigate to the system information page (typically Settings > System > About or Device Info). Alternatively, check the physical device label for the model number.
    Affected if The model is VIGI NVR1104H-4P V1 or VIGI NVR2016H-16MP V2.
  2. Check firmware version in web interface
    In the NVR web interface, go to Settings > System > About or Device Information page to view the current firmware version and build number.
    Affected if The firmware version is displayed and can be compared.
  3. Compare version to affected range for VIGI NVR1104H-4P V1
    If the device is VIGI NVR1104H-4P V1, compare your installed version to version 1.1.5 Build 250518. Versions earlier than 1.1.5 Build 250518 are affected.
    Affected if The firmware version is earlier than 1.1.5 Build 250518 (e.g., 1.1.4, 1.1.3, etc.).
  4. Compare version to affected range for VIGI NVR2016H-16MP V2
    If the device is VIGI NVR2016H-16MP V2, compare your installed version to version 1.3.1 Build 250407. Versions earlier than 1.3.1 Build 250407 are affected.
    Affected if The firmware version is earlier than 1.3.1 Build 250407 (e.g., 1.3.0, 1.2.x, etc.).

You are affected if your device is a VIGI NVR1104H-4P V1 with firmware before 1.1.5 Build 250518, or a VIGI NVR2016H-16MP V2 with firmware before 1.3.1 Build 250407.

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

Apply the vendor-supplied firmware updates to remediate: update VIGI NVR1104H-4P V1 to 1.1.5 Build 250518 or later, and VIGI NVR2016H-16MP V2 to 1.3.1 Build 250407 or later.

Recommended fix High confidence

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

  1. 1. Identify the specific VIGI NVR model (VIGI NVR1104H-4P V1 or VIGI NVR2016H-16MP V2) in use.
  2. 2. Check the current firmware version by accessing the NVR web interface or admin panel.
  3. 3. Download the corresponding fixed firmware from the official TP-Link support website: VIGI NVR1104H-4P V1 version 1.1.5 Build 250518 or VIGI NVR2016H-16MP V2 version 1.3.1 Build 250407.
  4. 4. Upload the firmware file through the NVR's firmware upgrade function in the web interface.
  5. 5. Wait for the upgrade process to complete and the device to reboot.
  6. 6. Verify the new firmware version is installed and the device is functioning normally.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7724 — 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-7724 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