dbcve.org
Ip7137 FirmwareOperating system · Vivotek

CVE-2025-66051

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Vivotek IP7137 camera with firmware version 0200a is vulnerable to path traversal. It is possible for an authenticated attacker to access resources beyond webroot directory using a direct HTTP request. Due to CVE-2025-66050, a password for administration panel is not set by default. The vendor has not replied to the CNA. Possibly all firmware versions are affected. Since the product has met End-Of-Life phase, a fix is not expected to be released.

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

Vivotek IP7137 IP camera firmware 0200a contains a path traversal vulnerability allowing authenticated attackers to access files outside the webroot directory via crafted HTTP requests. Combined with CVE-2025-66050 which leaves the admin panel password unset by default, unauthenticated attackers can easily gain the required authentication.

MitigationSince the product is End-of-Life with no vendor patch forthcoming, replace the device with a supported model or implement strict network segmentation and firewall rules restricting access to trusted networks only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ip7137 FirmwareOperating system
Affected:= 0200a

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 camera's web interface or check the device label/metadata to confirm the model is Vivotek IP7137
    Affected if The device is not a Vivotek IP7137
  2. Check the firmware version
    Log into the camera web interface and navigate to System > System Information, or use the RTSP/SNMP interface to retrieve the firmware version. Compare against version 0200a.
    Affected if The installed firmware is version 0200a
  3. Verify admin account status
    Attempt to log into the admin panel without providing a password, or check if the admin password field is blank/unset in the device configuration. For CVE-2025-66050, the default configuration leaves the password unset.
    Affected if The admin account has no password set or uses a default/blank password, allowing unauthenticated access
  4. Confirm web server is accessible
    Verify the camera's HTTP web interface is accessible on the network. The path traversal vulnerability is exploited via crafted HTTP requests to the web server.
    Affected if The web interface is exposed and accessible

You are affected if you have a Vivotek IP7137 camera running firmware version 0200a with the admin password unset or on default settings, as this combination allows unauthenticated path traversal exploitation.

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

Since the product is End-of-Life with no vendor patch forthcoming, replace the device with a supported model or implement strict network segmentation and firewall rules restricting access to trusted networks only.

Recommended fix High confidence
  1. Isolate the device on a restricted VLAN or behind a firewall to limit network exposure
  2. If the web interface is not required, disable it or block HTTP/HTTPS ports at the network perimeter
  3. Implement IP address whitelisting on adjacent firewall or network device to restrict access to authorized management IPs
  4. Monitor access logs for suspicious path traversal requests (e.g., ../, ../../)
  5. Consider replacing the EOL device with a currently supported camera model from Vivotek or an alternative vendor
  6. If continued use is mandatory, place device in a dedicated network segment with strict ingress/egress filtering
Caveat Device is End-of-Life with no vendor support; replacement is the only long-term solution

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

Fix this in Ip7137 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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