In theory, there may be a solution for this.
- Insert a unique CSRF token into each custom bookmarklet.
- Wrap the code in a bookmark in an anonymous function so that the page does not have access to it.
- - . , , .
- XMLHttpRequest :
- :
- , .
: - , (, Array()), - - , / , userID CSRF.