Wordpress “Nextend Twitter Connect” =================================== Document Title: =============== WordPress “Nextend Twitter Connect” Plugin Version: 1.5.1 is vulnerable to Reflected XSS (Cross Site Scripting) Download URL: ============= http://ift.tt/14v5QQx Release Date: ============= 2015-06-20 Vulnerability CVE ID: ===================== CVE-2015-4557 Vulnerability Disclosure Timeline: ================================== 2015 – 06 – 15 First notified to WordPress. 2015 – 06 – 15 First notified to plugin vendor . 2015 – 06 – 15 First notified to Mitre for CVE number. 2015 – 06 – 16 Vendor publish update for the plugin. 2015 – 06 – 22 Public Disclosure. Discovery Status: ================= Published Severity Level: =============== High Technical Details, Description & Proof of Concept (PoC): ======================================================== After installing Wordpress I add the plugin "Nextend Twitter Connect" witch allow you to login Wordpress with Twitter account. During my test I find out that the “redirect_to” parameter is vulnerable to Reflected XSS attack. http://ift.tt/1Lsioe0 To reach to root of the problem, I took a look in the plugin source code and realized that the “new_Twitter_sign_button” witch located in the file “nextend-Twitter-connect.php”. The problematic function are locate in line 492: http://ift.tt/1GFDOjJ As you can see in the line 492, the function don’t escapes HTML tags or other dangerous symbols. When attacker injects the Javascript code in the URL the function runs the code, as you can see: http://ift.tt/1Lsioe2 And pop the alert window. Solution - Fix & Patch: ======================= In order to solve this security flaw you need to add the “htmlentities” function. (http://ift.tt/11pVKOE) As you can see in the image: http://ift.tt/1GFDOjL Wordpress “Nextend Google Connect” =================================== Document Title: =============== WordPress “Nextend Google Connect” Plugin Version: 1.5.1 is vulnerable to Reflected XSS (Cross Site Scripting) Download URL: ============= http://ift.tt/1Lsimmr Release Date: ============= 2015-06-20 Vulnerability CVE ID: ===================== CVE-2015-4557 Vulnerability Disclosure Timeline: ================================== 2015 – 06 – 15 First notified to WordPress. 2015 – 06 – 15 First notified to plugin vendor . 2015 – 06 – 15 First notified to Mitre for CVE number. 2015 – 06 – 16 Vendor publish update for the plugin. 2015 – 06 – 22 Public Disclosure. Discovery Status: ================= Published Severity Level: =============== High Technical Details, Description & Proof of Concept (PoC): ======================================================== After installing Wordpress I add the plugin "Nextend Google Connect" witch allow you to login Wordpress with Google account. During my test I find out that the “redirect_to” parameter is vulnerable to Reflected XSS attack. http://ift.tt/1GFDQIs To reach to root of the problem, I took a look in the plugin source code and realized that the “new_google_sign_button” witch located in the file “nextend-Google-connect.php”. The problematic function are locate in line 433: http://ift.tt/1Lsimmv As you can see in the line 433, the function don’t escapes HTML tags or other dangerous symbols. When attacker injects the Javascript code in the URL the function runs the code, as you can see: http://ift.tt/1GFDOjN And pop the alert window. Solution - Fix & Patch: ======================= In order to solve this security flaw you need to add the “htmlentities” function. (http://ift.tt/11pVKOE) As you can see in the image: http://ift.tt/1Lsioea Liran Segal (Bugsec Information Security LTD) Regards, Liran Segal Penetration Testing BugSec Cyber & Information Security
Source: Gmail -> IFTTT-> Blogger
No comments:
Post a Comment