AskApache 3.0 Cross Site Request Forgery Vulnerability

2013-12-27T00:00:00
ID 1337DAY-ID-21717
Type zdt
Reporter High-Tech Bridge
Modified 2013-12-27T00:00:00

Description

AskApache Firefox Adsense WordPress plugin version 3.0 suffers from a cross site request forgery vulnerability.

                                        
                                            Product: AskApache Firefox Adsense Wordpress plugin
Vendor: AskApache
Vulnerable Version(s): 3.0 and probably prior
Tested Version: 3.0
Advisory Publication:  December 5, 2013  [without technical details]
Vendor Notification: December 5, 2013 
Public Disclosure: December 26, 2013 
Vulnerability Type: Cross-Site Request Forgery [CWE-352]
CVE Reference: CVE-2013-6992
Risk Level: Low 
CVSSv2 Base Score: 2.6 (AV:N/AC:H/Au:N/C:N/I:P/A:N)
Solution Status: Not Fixed
Discovered and Provided: High-Tech Bridge Security Research Lab ( https://www.htbridge.com/advisory/ ) 

-----------------------------------------------------------------------------------------------

Advisory Details:

High-Tech Bridge Security Research Lab discovered vulnerability in AskApache Firefox Adsense Wordpress plugin, which can be exploited to perform Сross-Site Request Forgery (CSRF) attacks.


1) Сross-Site Request Forgery (CSRF) in AskApache Firefox Adsense Wordpress plugin: CVE-2013-6992

The vulnerability exists due to insufficient verification of the HTTP request origin in "/wp-admin/options-general.php" script. A remote attacker can trick a logged-in administrator to visit a specially crafted page with CSRF exploit, inject and execute arbitrary HTML and script code in administrator’s browser in context of vulnerable website. 

The exploitation example below injects JavaScript code, which uses the "alert()" function to display "immuniweb" word:


<form action="http://[host]/wp-admin/options-general.php?page=askapache-firefox-adsense.php" method="post" name="main">
<input type="hidden" name="aafireadcode"  value='<script>alert("immuniweb");</script>'>
<input type="submit" id="btn">
</form>


-----------------------------------------------------------------------------------------------

Solution:

Disable the vulnerable plugin. 

On 2013-12-06 vendor replied to our notification that he will not support the plugin anymore, and proposed to remove the vulnerable plugin as the official solution. The vendor has also taken steps to remove this plugin from WordPress.org.

#  0day.today [2018-04-02]  #