------------------------------------------------------------------------ Cross-Site Scripting vulnerability in Google Maps WordPress Plugin ------------------------------------------------------------------------ Julien Rentrop, July 2016 ------------------------------------------------------------------------ Abstract ------------------------------------------------------------------------ A Cross-Site Scripting vulnerability was found in the Google Maps WordPress Plugin. This issue allows an attacker to perform a wide variety of actions, such as stealing users' session tokens, or performing arbitrary actions on their behalf. In order to exploit this issue, the attacker has to lure/force a victim into opening a malicious website/link. ------------------------------------------------------------------------ OVE ID ------------------------------------------------------------------------ OVE-20160712-0038 ------------------------------------------------------------------------ Tested versions ------------------------------------------------------------------------ This issue was successfully tested on Google Maps [2] WordPress Plugin version 2.1.2. ------------------------------------------------------------------------ Fix ------------------------------------------------------------------------ This issue is resolved in Google Maps version 2.1.4 [3]. ------------------------------------------------------------------------ Introduction ------------------------------------------------------------------------ The Google Maps [2] WordPress Plugin is a simple and effective tool for rapid creation of individual Google Maps in posts and pages. A Cross-Site Scripting vulnerability was found in the Google Maps WordPress Plugin. This issue allows an attacker to perform a wide variety of actions, such as stealing users' session tokens, or performing arbitrary actions on their behalf. In order to exploit this issue, the attacker has to lure/force a victim into opening a malicious website/link. ------------------------------------------------------------------------ Details ------------------------------------------------------------------------ This issue exists due to the lack of output encoding on the id URL parameter. The vulnerable code fragment is listed below: