How to fix: WebSocket connection without origin validation
A WebSocket endpoint does not validate the Origin header, allowing connections from any website.
Why it matters
Without Origin validation, any website can open a WebSocket connection to your server using the victim's cookies, a cross-site WebSocket hijacking attack that gives attackers full access to any WebSocket API the user can reach.
WebSocket connections bypass CORS restrictions. The server must check the Origin header and reject connections from unexpected origins.
How to fix it
- 1Check the Origin header on WebSocket upgrade requests
- 2Reject connections from origins not in your allowlist
- 3Use a CSRF token in the WebSocket connection URL or initial handshake message
Code examples
Validate WebSocket origin server-side
// Node.js WebSocket server: reject unexpected origins
const { WebSocketServer } = require('ws');
const wss = new WebSocketServer({
verifyClient({ origin }) {
return origin === 'https://example.com';
},
});References
Detected automatically by VulnRadar. The check id is cross-site-websocket, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is WebSocket connection without origin validation?
- VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id cross-site-websocket, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does WebSocket connection without origin validation map to?
- It maps to CWE-346. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.