CVE-2026-13125
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 · uneditedGeoWebPlayer (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. In order to access the websocket server, no authentication is required. As such, any malicious website can attempt to open a connection to the server and potentially access sensitive APIs. In particular, it's possible to call a combination of the `create` method and `getScreenCapture` to retrieve the content of the user's screen.
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 confidenceGeoWebPlayer creates an unauthenticated websocket server that accepts connections from any website, allowing malicious pages to call sensitive APIs including screen capture via the `create` and `getScreenCapture` methods without user consent or authentication.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify GeoWebPlayer installationSearch for GeoWebPlayer application files, services, or processes on the system. Check common installation directories or look for a process named 'GeoWebPlayer' or similar.Affected if GeoWebPlayer is found to be installed or running on the system
-
Locate and inspect websocket configurationFind the configuration files for GeoWebPlayer (typically in the application install directory or config folder). Look for websocket server settings, particularly any configuration files handling websocket connections, port bindings, or network settings.Affected if Websocket configuration files exist and show the server binds to a network interface accessible to web browsers (e.g., localhost, 0.0.0.0, or external IP)
-
Check websocket authentication settingsExamine the websocket server initialization code or configuration to determine if authentication (token-based, session-based, or other) is required before accepting connections. Look for authentication-related parameters or middleware in the websocket handling code.Affected if No authentication mechanism is required to connect to the websocket server, or authentication is disabled/missing
-
Verify origin/CORS restrictionsInspect the websocket server code or configuration for origin validation, CORS settings, or same-origin policy enforcement. Check if the server validates the Origin header or restricts connections to trusted origins.Affected if The websocket accepts connections from any origin (no origin validation, wildcard '*' allowed, or CORS disabled)
-
Confirm vulnerable API exposureTest the websocket API by attempting to call the 'create' and 'getScreenCapture' methods without providing any credentials or authentication token. Observe if these methods execute and return screen capture data.Affected if The 'create' and 'getScreenCapture' methods are accessible and functional without any authentication token or valid credentials
The environment is affected if GeoWebPlayer is installed with an unauthenticated websocket server that accepts connections from any origin and exposes the create/getScreenCapture methods without requiring authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement websocket authentication (e.g., token-based or session-based) and/or restrict websocket connections to trusted origins using appropriate CORS or same-origin policy controls.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13125 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13125 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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