WP Google Maps Pro <= 8.1.11 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 8.1.12
- Affected Plugin
- WP Google Maps Pro
- Affected Version
<= 8.1.11- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-36871
At a glance
CVE-2021-36871 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Google Maps Pro WordPress plugin, affecting versions <= 8.1.11. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 8.1.12; sites on affected versions should update now. Disclosed September 2021, reported by R3N0.
Vulnerability Overview
Multiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in WordPress WP Google Maps Pro premium plugin (versions <= 8.1.11). Vulnerable parameters: &wpgmaps_marker_category_name, Value > &attributes[], Name > &attributes[], &icons[], &names[], &description, &link, &title.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP Google Maps Pro <= 8.1.11 takes any authenticated account. 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 WP Google Maps Pro the fix is 8.1.12: builds <= 8.1.11 are affected, anything from 8.1.12 onward is not.
Remediation
Update to version 8.1.12, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Google Maps Pro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Google Maps Pro 8.1.12 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C