dbcve.org
CWE-129Weakness · CWE-129

CVE-2026-13131

HIGH · 8.3 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 8 weeks old

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
GeoWebPlayer (also called "Web Plugin" in the GV-VMS documentation and "WS Player" for VMS-Cloud) is an addon that can be installed with various GeoVision software (GV-VMS, GV-Cloud, ...). It creates a websocket server that expands the capabilities of the various web-interfaces provided by the GeoVision software and may be necessary for them to function properly. The Websocket server can accept various commands coming from localhost. Many of the commands will take an `index` value that is then used to access various arrays to enter critical sections, perform various actions via function calls, etc. However the `index` value is usually not checked for valid range, and as such it can be used to access multiple arrays out-of-bound. #### connectInfo command index-out-of-bound

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

GeoWebPlayer websocket server fails to validate the 'index' parameter in various commands before using it to access arrays. This allows an attacker with local access to the websocket server to read or write beyond array boundaries by providing out-of-range index values, potentially leading to memory corruption, information disclosure, or denial of service.

MitigationRestrict access to the localhost websocket interface to trusted local processes only, and implement proper bounds checking on all index parameters before array access. Consider network segmentation to limit local 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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 if GeoWebPlayer is installed
    Search for GeoWebPlayer software on the system using package managers, installed programs lists, or file system searches for GeoWebPlayer-related directories or executables
    Affected if GeoWebPlayer is found installed on the system
  2. Determine the installed version
    Locate the GeoWebPlayer version information through the application's about dialog, version file, executable properties, or package manager listing
    Affected if The installed version matches or falls within an affected version range (compare to known vulnerable versions if available)
  3. Verify the websocket server is enabled
    Check GeoWebPlayer configuration files, running processes, or service settings to determine if the websocket server component is active
    Affected if The websocket server is running and listening on a network interface
  4. Check websocket access controls
    Examine the websocket server configuration to determine authentication requirements and permitted client origins or IP addresses
    Affected if The websocket interface allows unauthenticated access or accepts connections from untrusted local processes
  5. Assess local attack surface
    Review which local users or processes have network access to the websocket server port (typically localhost or local interface)
    Affected if Untrusted local users or processes can connect to the websocket server

The environment is affected if GeoWebPlayer with a vulnerable websocket server version is installed, the websocket interface is accessible, and untrusted local actors can interact with it without proper validation of index parameters.

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

Restrict access to the localhost websocket interface to trusted local processes only, and implement proper bounds checking on all index parameters before array access. Consider network segmentation to limit local attack surface.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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