GV-LPC2011/LPC2211: Incorrect Privilege Assignment
CVE-2026-42368 is a critical-severity incorrect privilege assignment vulnerability in GV-LPC2011/LPC2211 from GeoVision, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected GV-LPC2011/LPC2211 versions: 1.10. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of GV-LPC2011/LPC2211 you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on geovision.com.tw for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GeoVision | GV-LPC2011/LPC2211 | 1.10 | Not stated |
| Geovision | Gv-lpc2011 Firmware | 1.10 | Not stated |
| Geovision | Gv-lpc2211 Firmware | 1.10 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.
Official description
A privilege escalation vulnerability exists in the Web Interface functionality of GeoVision LPC2011/LPC2211 1.10. A specially crafted HTTP request can lead to execute priviledged operation. An attacker can visit a webpage to trigger this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Privilege Assignment
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
More Incorrect Privilege Assignment vulnerabilities (CWE-266)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Other vulnerabilities in GV-LPC2011/LPC2211
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.4 Critical severity
- 7.2 High severity
Recent Incorrect Privilege Assignment vulnerabilities
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 8.8 High severity
- 9.8 Critical severity
- 7.3 High severity
Spotted an error? Tell us.