Google Maps <= 2.1.3 - Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1.4
- Affected Plugin
- Google Maps
- Affected Version
<= 2.1.3- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Google Maps WordPress plugin, affecting versions <= 2.1.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.1.4; sites on affected versions should update now. Disclosed August 2016, reported by Julien Rentrop.
Vulnerability Overview
The Google Maps plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'id' URL parameter in versions up to, and including, 2.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Google Maps <= 2.1.3 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Google Maps the fix is 2.1.4: builds <= 2.1.3 are affected, anything from 2.1.4 onward is not.
Remediation
Update to version 2.1.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Google Maps: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Google Maps 2.1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C