One thing I've seen a lot that develops as a function and is not considered a security hole until it changes the state of GET requests too late. This can easily lead to fake cross-site search requests . For example, your application may have a link to http://mysite.com/logout , which registers users. But a third-party site can add this code:
<img src="http://mysite.com/logout">
Then, when users load the page on evil.com, they exit mysite.com!
, API, GET. , URL-, site.com/addfriend, site.com/sendmessage .., URL- , , API .