WebSockets don't follow the Same-Origin Policy. This means that if the application relies on cookies (or Basic authentication) to perform authentication/authorization, a malicious website can get a victim to access this application via a WebSocket and potentially access/modify sensitive data as this user.
I created a Proof of Concept (malicious html-page) allowing read logs through this vulnerability.
WebSockets don't follow the Same-Origin Policy. This means that if the application relies on cookies (or Basic authentication) to perform authentication/authorization, a malicious website can get a victim to access this application via a WebSocket and potentially access/modify sensitive data as this user.
I created a Proof of Concept (malicious html-page) allowing read logs through this vulnerability.
More information about the vulnerability you can find here: https://portswigger.net/web-security/websockets/cross-site-websocket-hijacking
To prevent this issue, the Origin header check was added.