One more reason to use NoScript - it would have made the CSRF significantly harder to pull off. And a reason to use an OS with a proper package manager, of course ;)
Not really. Depending on the protocol CSRFs are often an easy 1-click exploit on noscript-enabled browsers. Something like this: " /> Is the corresponding 1-click that works on noscript.
That said, it would still require the victim to load the fake LinkedIn page (with the wrong domain), which is more likely to look suspicious.
And it would've loaded the router page after the POST (instead of redirecting to LinkedIn), which would definitively signal that something was wrong.