I've been looking into the security risks that needed to be addressed when setting up an application using websockets, but the major issues I've looked at (CSRF, XSS, cross-site websocket hijacking) all seem to hinge on the websocket client being set up in a browser. Csrf and web-socket hijacking both seem to hinge on other websites being able to access cookie information from the targeted website, but this shouldn't be an issue when the websocket client is a separate, non-browser application. As for XSS vulnerabilities, I don't know how a non-browser client introduces any new issues.
Can any of these issues be ignored when building a websocket application that works outside browsers? Are there any new risks that arise when only using websockets to communicate with non-browser clients?