I won't provide a source but i'll provide a modified real life example, since i'm pretty sure this vuln is still in the wild. I was doing a pen test on a route

I won't provide a source but i'll provide a modified real life example, since i'm pretty sure this vuln is still in the wild. I was doing a pen test on a router whose manufacturer decided it would be an OK idea to use GET requests to launch their ping diagnostic tool on their router's unauthenticated QA web interface. this ping diagnostic tool was triggered by doing GET http://192.168.1.1/diagnostic/trace&ip=X.X.X.X http://192.168.1.1/diagnostic/trace&ip=X.X.X.X The IP address in the URL parameter would get plugged directly into a "ping" command line command, so you could obtain command injection by going GET http://192.168.1.1/diagnostic/trace&ip=X.X.X.X&&telnetd http://192.168.1.1/diagnostic/trace&ip=X.X.X.X&&telnetd You could exploit this from literally any website on the internet, and since it's a GET request and we don't care about what it returns, CORS won't save your router. I think that counts as a javascript one-liner, but you get the idea how fucking awful some of these routers are.