dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-12851

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
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
Multiple OS command injection vulnerabilities exist in the libNetSetObj.so functionality of GeoVision GV-I/O Box 4E 2.09. A specially crafted network packet can lead to command execution. An attacker can send a network request to trigger this vulnerability. `libNetSetObj.so` is an internal library used by various binaries on the device to configure the network stack (start and stop various services, configure IP, Netmask, gateway, dns, etc.) #### CNetSetObj::m_F_n_Set_DNS_Addr command injection The following function can take up to two addresses, performs no sanitization and then calls `system`. This is a classic command injection vulnerability. The function is reachable from both the network-exposed `DVRSearch` service and the `Network.cgi` endpoint. int __fastcall CNetSetObj::m_F_n_Set_DNS_Addr(CNetSetObj *this, char *dns1, char *dns2) { int result; // r0 char v5[80]; // [sp+0h] [bp-50h] BYREF if ( !dns1 ) result = 0; if ( dns1 ) { sprintf(v5, "/bin/echo nameserver %s > /etc/resolv.conf", dns1); // attacker controlled dns1 field system(v5); if ( dns2 ) { sprintf(v5, "/bin/echo nameserver %s >> /etc/resolv.conf", dns2); system(v5); } return 1; } return result;

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

OS command injection vulnerability in GeoVision GV-I/O Box 4E firmware 2.09 allows remote attackers to execute arbitrary commands via unsanitized dns1 and dns2 parameters passed to system() calls in the CNetSetObj::m_F_n_Set_DNS_Addr function. The vulnerability is exposed through both the DVRSearch service and Network.cgi endpoint, enabling unauthenticated remote code execution with CVSS 9.1 severity.

MitigationApply vendor firmware patch if available; otherwise, isolate the device on a restricted network segment or disable the DVRSearch/Network.cgi services to reduce attack surface.

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

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

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 device model and firmware version
    Access the device's web interface or check the device label/metadata to confirm it is a GeoVision GV-I/O Box 4E. Look for the firmware version displayed in the system information or status page.
    Affected if The device model is GV-I/O Box 4E and the firmware version is 2.09 or earlier.
  2. Confirm DVRSearch service is accessible
    Check if port 5552 (typical DVRSearch port for GeoVision devices) is open and reachable on the device. Use a network scanner or telnet/nc to test connectivity to that port.
    Affected if The DVRSearch service port is exposed and accessible from an untrusted network.
  3. Verify Network.cgi endpoint is reachable
    Attempt to access the Network.cgi endpoint via HTTP/HTTPS (typically at /cgi-bin/cgiro/Network.cgi or similar path) from the network. Check if the device responds to requests on that endpoint.
    Affected if The Network.cgi endpoint is accessible over the network without authentication restrictions.
  4. Inspect DNS configuration interface
    If accessible, examine the DNS settings page in the device web interface or query the device for current dns1/dns2 values to understand if user-controlled input is accepted.
    Affected if The device accepts DNS server parameters through a web interface or API without input validation indicators.

A user is affected if they have a GeoVision GV-I/O Box 4E running firmware 2.09 or earlier, with the DVRSearch service or Network.cgi endpoint exposed on an accessible network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch if available; otherwise, isolate the device on a restricted network segment or disable the DVRSearch/Network.cgi services to reduce attack surface.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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