dbcve.org
CWE-129Weakness · CWE-129

CVE-2026-57264

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. #### setPIP 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

The GeoWebPlayer websocket server fails to validate the index parameter in commands like setPIP, allowing attackers to access arrays out-of-bounds. This missing bounds check on array indices can lead to memory corruption, potential code execution, or denial of service.

MitigationRestrict local access to the GeoWebPlayer websocket server to trusted local processes only. Monitor for vendor patches and apply them when available.

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. Confirm GeoWebPlayer is installed
    Search for GeoWebPlayer in installed programs (Windows: Programs and Features, Linux: dpkg -l or rpm -qa), or look for GeoWebPlayer executables and installation directories
    Affected if GeoWebPlayer is found on the system
  2. Identify the websocket server component
    Locate the GeoWebPlayer installation directory and identify the websocket server executable or module (commonly named geowebplayer.exe, geowebplayer, or similar). Check for open network ports using 'netstat -an | grep <port>' or review configuration files for websocket bind addresses
    Affected if A websocket server component is running or configured to run
  3. Verify the setPIP command is accessible
    If you can interact with the websocket server, send a test message to invoke the setPIP command with a valid index value to confirm the command interface is exposed. Check documentation or binary analysis for command handlers
    Affected if The setPIP command handler is present and reachable
  4. Test for index validation vulnerability
    Send a websocket message to the setPIP command with an out-of-bounds index value (e.g., negative number, very large number, or beyond array bounds) and observe the response or system behavior. Monitor for crashes, errors, or unexpected memory access
    Affected if Out-of-bounds index values are accepted without validation and cause crashes, errors, or unexpected behavior
  5. Check if websocket server accepts external connections
    Review configuration files and network settings to determine if the websocket server binds to all interfaces (0.0.0.0) or localhost only, and whether authentication or process restrictions are configured
    Affected if The websocket server accepts commands from untrusted sources or is exposed to network access

A user is affected if GeoWebPlayer with a websocket server is running and the setPIP command accepts unvalidated index parameters that cause out-of-bounds array access.

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 local access to the GeoWebPlayer websocket server to trusted local processes only. Monitor for vendor patches and apply them when available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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