WP Google Maps <= 9.0.27 - Unauthenticated Stored Cross-Site Scripting via REST API
Strategic Overview
- Status
- Patched in 9.0.28
- Affected Plugin
- WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- Affected Version
<= 9.0.27- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-6627
At a glance
CVE-2023-6627 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Go Maps WordPress plugin, affecting versions <= 9.0.27. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 9.0.28; sites on affected versions should update now. Disclosed December 2023, reported by Marc-Alexandre Montpas.
Vulnerability Overview
The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API in all versions up to, and including, 9.0.27 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP Go Maps <= 9.0.27 takes no account at all. 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 Go Maps the fix is 9.0.28: builds <= 9.0.27 are affected, anything from 9.0.28 onward is not.
Remediation
Update to version 9.0.28, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Go Maps 9.0.28 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2025-11307: Google Maps <= 9.0.47 Stored Cross-Site Scripting
CVE-2025-11307 - 6.4CVE-2026-4268: WP Go Maps Authenticated (Subscriber+) Stored XSS
CVE-2026-4268 - 6.4CVE-2024-5994: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-5994 - 6.4CVE-2024-3557: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-3557
Other vulnerabilities in WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- 9.8CVE-2019-10692: WP Go Maps (formerly WP Google Maps) SQL Injection
CVE-2019-10692 - 7.5CVE-2026-84780: WP Go Maps DoS
CVE-2026-84780 - 7.5CVE-2026-15381: WP Go Maps SQL Injection
CVE-2026-15381 - 6.4CVE-2024-1582: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-1582 - 6.4WP Google Maps <= 6.3.14 Stored Cross-Site Scripting
- 6.1CVE-2024-29931: WP Google Maps <= 9.0.29 Reflected XSS
CVE-2024-29931 - 6.1CVE-2023-6697: WP Go Maps (formerly WP Google Maps) Reflected XSS
CVE-2023-6697 - 6.1CVE-2019-14792: WP Google Maps <= 7.11.34 CSRF to Cross-Site Scripting
CVE-2019-14792
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C