dbcve.org
CWE-129Weakness · CWE-129

CVE-2026-57267

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. #### snapshot 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's websocket server accepts commands with an index parameter that is used to access arrays without proper bounds validation. This allows out-of-bounds array access when an attacker provides an index value outside the valid range, potentially leading to memory corruption, information disclosure, or denial of service.

MitigationImplement rigorous bounds checking on all index parameters before array access in the websocket command handlers, or apply vendor-supplied patches to GeoWebPlayer. Network segmentation should limit websocket server access to trusted localhost sources.

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. Verify GeoWebPlayer installation exists
    Search for GeoWebPlayer in your system by checking installed programs, running services, or common installation directories. Look for process names or executables containing 'geowebplayer' or similar variations.
    Affected if GeoWebPlayer is installed and running on the system
  2. Confirm websocket server is enabled
    Locate GeoWebPlayer configuration files (such as config.xml, settings.conf, or similar) and check whether the websocket server component is explicitly enabled. Look for settings like 'enableWebsocket', 'websocketServer', or similar boolean flags.
    Affected if The websocket server feature is enabled in GeoWebPlayer configuration
  3. Determine installed GeoWebPlayer version
    Check the GeoWebPlayer installation for version information in its executable, about dialog, version file, or log files. Compare the discovered version against any known release notes or patch information.
    Affected if The installed version lacks the bounds checking fix for index parameters in websocket handlers
  4. Inspect websocket command handler configuration
    Examine GeoWebPlayer configuration or source code files related to websocket command processing. Identify if there are specific command handlers that accept index parameters and whether bounds validation logic is present.
    Affected if Websocket command handlers process index parameters without documented bounds validation code

A user is affected if GeoWebPlayer is installed with its websocket server enabled and the installed version does not include proper index bounds checking in websocket command handlers.

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

Implement rigorous bounds checking on all index parameters before array access in the websocket command handlers, or apply vendor-supplied patches to GeoWebPlayer. Network segmentation should limit websocket server access to trusted localhost sources.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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