WP Google Maps <= 7.11.27 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 7.11.28
- Affected Plugin
- WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- Affected Version
< 7.11.28- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Go Maps WordPress plugin, affecting versions < 7.11.28. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 7.11.28; sites on affected versions should update now. Disclosed June 2019.
Vulnerability Overview
The WP Google Maps plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 7.11.27. This is due to missing nonce validation on the wpgmza_settings_page_post() function. This makes it possible for authenticated attackers to modify the plugin's settings.
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-352: Cross-Site Request Forgery (CSRF)
WP Go Maps < 7.11.28 carries this weakness at wpgmza_settings_page_post(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Go Maps the fix is 7.11.28: builds < 7.11.28 are affected, anything from 7.11.28 onward is not.
Remediation
Update to version 7.11.28, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Go Maps: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Go Maps 7.11.28 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
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 - 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 - 6.4CVE-2024-1582: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-1582
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C