GeoVision GV-LPC2011/LPC2211 up to 1.10 Web Interface predictable state
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in GeoVision GV-LPC2011 and LPC2211 up to 1.10. This affects an unknown function of the component Web Interface. The manipulation leads to predictable state. This vulnerability is traded as CVE-2026-42365. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in GeoVision GV-LPC2011 and LPC2211 up to 1.10. This issue affects some unknown functionality of the component Web Interface. The manipulation with an unknown input leads to a predictable state vulnerability. Using CWE to declare the problem leads to CWE-341. A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc. Impacted is confidentiality. The summary by CVE is:
A guessable session cookie vulnerability exists in the Web Interface functionality of GeoVision LPC2011/LPC2211 1.10. A specially crafted series of HTTP requests can lead to an authentication bypas. An attacker can bruteforce session cookies to trigger this vulnerability.
The weakness was shared by Philippe Laulheret. The advisory is shared at geovision.com.tw. The identification of this vulnerability is CVE-2026-42365 since 04/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
Upgrading to version 1.12 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 8.6
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Predictable stateCWE: CWE-341 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: GV-LPC2011/LPC2211 1.12
Timeline
04/27/2026 CVE reserved05/04/2026 Advisory disclosed
05/04/2026 VulDB entry created
06/15/2026 VulDB entry last update
Sources
Advisory: geovision.com.twResearcher: Philippe Laulheret
Status: Confirmed
CVE: CVE-2026-42365 (🔒)
GCVE (CVE): GCVE-0-2026-42365
GCVE (VulDB): GCVE-100-360929
Entry
Created: 05/04/2026 06:30Updated: 06/15/2026 23:31
Changes: 05/04/2026 06:30 (63), 06/15/2026 23:31 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.