3 ms·
That form wouldn't be on the same domain and therefore would hit CSRF protections.
by Someone1234 12y ago
That form wouldn't be on the same domain and therefore would hit CSRF protections.
- Ded7xSEoPKYNsDd 12y agoYes, if you require a user-specific random token in the request, the exploit doesn't work. But that's independent of GET/POST and not what you said in your earlier post.