>>/29868/
Wouldn't this be easily avoidable with a proper content security policy?