WP Go Maps (formerly WP Google Maps) <= 10.0.05 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting via admin_post_wpgmza_save_settings
Strategic Overview
- Status
- Patched in 10.0.06
- Affected Plugin
- WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- Affected Version
<= 10.0.05- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-4268
At a glance
CVE-2026-4268 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 <= 10.0.05. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 10.0.06; sites on affected versions should update now. Disclosed March 2026, reported by bashu.
Vulnerability Overview
The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘wpgmza_custom_js’ parameter in all versions up to, and including, 10.0.05 due to insufficient input sanitization and output escaping and missing capability check in the 'admin_post_wpgmza_save_settings' hook anonymous function. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
WP Go Maps <= 10.0.05 carries this weakness at wpgmza_custom_js, and reaching it takes an account at Subscriber level or above. 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 10.0.06: builds <= 10.0.05 are affected, anything from 10.0.06 onward is not.
Remediation
Update to version 10.0.06, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Go Maps 10.0.06 closes this, and updating the plugin is the step that ends it.
- Firewall
- 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-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
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.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-2023-6627: WP Google Maps <= 9.0.27 Stored Cross-Site Scripting
CVE-2023-6627 - 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