What is the CVSS score of CVE-2026-57872?

CVE-2026-57872 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 1.0%.

Which versions of GeoVision GV-LPC2011 are affected by CVE-2026-57872?

GeoVision license plate recognition appliances (GV-LPC2011, GV-LPC2211) with firmware V1.12 and earlier contain an unauthenticated remote file read vulnerability allowing attackers to retrieve…

How to fix or mitigate CVE-2026-57872?

Within 24 hours: Identify and document all GV-LPC2011 and GV-LPC2211 appliances on the network, noting firmware versions. Within 7 days: Restrict network access through firewall rules and network segmentation-isolate devices to management VLANs or trusted networks only; disable remote access if not operationally required. Within 30 days: Monitor GeoVision security advisories for firmware patches (target V1.13+); establish contingency plan for device replacement or retirement if patch timeline extends beyond risk tolerance.

GeoVision GV-LPC2011 CVE-2026-57872

EUVD-2026-39628 HIGH

Path Traversal (CWE-22)

2026-06-26 GV

GHSA-pwf5-hg39-g9g9

Information Disclosure Path Traversal Gv Lpclpc2011 2211 Geovision Inc

7.5

CVSS 3.1 · Vendor: GV

Severity by source

Vendor (GV) PRIMARY

7.5 HIGH

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

vuln.today AI

7.5 HIGH

Unauthenticated remote HTTP request (AV:N/AC:L/PR:N/UI:N) yields arbitrary file read, so C:H with no integrity or availability impact and unchanged scope.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GV).

CVSS VectorVendor: GV

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 26, 2026 - 08:15 vuln.today

DescriptionCVE.org

An unauthenticated directory traversal vulnerability exists in get_fcont.cgi in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by insufficient validation of user-supplied file path input before the requested file is accessed by the CGI component. A remote attacker may exploit this vulnerability by sending a crafted request to read arbitrary files accessible to the affected process, resulting in information disclosure.

AnalysisAI

Arbitrary file read in GeoVision GV-LPC2011 and GV-LPC2211 license plate recognition appliances (firmware V1.12 and earlier) lets a remote, unauthenticated attacker traverse the filesystem via the get_fcont.cgi endpoint and retrieve any file readable by the CGI process. Because the CGI fails to validate the user-supplied file path, a single crafted HTTP request can disclose configuration files, credentials, or other sensitive data. There is no public exploit identified at time of analysis, but the network-reachable, no-authentication nature (CVSS 7.5) makes it straightforward to weaponize.

Technical ContextAI

The affected components are GeoVision's GV-LPC2011 and GV-LPC2211 - embedded license plate recognition (LPR/ANPR) camera appliances that expose a web/CGI management interface. The flaw lives in get_fcont.cgi, a CGI handler whose purpose is to return file contents; it accepts a file path parameter and passes it to a file-access call without canonicalizing or sanitizing it. This is a textbook CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, 'Path Traversal') issue: by injecting sequences such as ../ the attacker escapes the intended content directory and reaches arbitrary files within the embedded Linux filesystem that the CGI's process UID can read. The single CPE provided, cpe:2.3:a:geovision_inc.:gv-lpclpc2011/2211:*, covers the LPC2011/2211 product line at the application layer.

RemediationAI

Upgrade the device firmware to the first release after V1.12 as published by GeoVision; consult the vendor advisory at https://www.geovision.com.tw/cyber_security.php for the exact patched version, since no precise fix version is confirmed in the available data (No vendor-released patch version independently confirmed at time of analysis). Until patched firmware is applied, remove the device management/CGI interface from the public internet and place it behind a VPN or management VLAN, restrict access to the get_fcont.cgi endpoint and the web interface to trusted source IPs via firewall/ACL, and front the device with a reverse proxy or WAF rule that rejects path-traversal sequences (../, encoded variants) in request parameters - noting that WAF filtering is a stopgap that determined attackers can sometimes encode around. The main trade-off of network isolation is loss of remote/cloud management convenience, which is acceptable given the unauthenticated file-disclosure exposure.