An attacker cannot gain anything by using cross-site scripting methods for himself. The purpose of cross-site scripting is to manipulate page elements that are displayed to the user in a malicious way, whether phishing or reading a cookie. In other words, an attack can only affect objects on the client side.
However, it’s important to remember what “a user ever looking at his own data” means.
Suppose I have a website where users can have their own profile, accessible only to themselves. The page has a text input element that allows users to enter the URL of their website. Now suppose the user profile update form uses GET.
A page refresh message might look like this:
http://www.example.com/privateprofile.pl?action=update&userwebpage=http://www.example.net
, URL-:
http://www.example.com/privateprofile.pl?action=update&userwebpage= [malicious_js_code_here]
, , , , . , , XSS . , XSS .