WP Go Maps <= 10.1.01 - Unauthenticated Arbitrary Record Creation
Strategic Overview
- Status
- Patched in 10.1.02
- Affected Plugin
- WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- Affected Version
<= 10.1.01- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-12238
At a glance
CVE-2026-12238 is a medium-severity Missing Authorization vulnerability in the WP Go Maps WordPress plugin, affecting versions <= 10.1.01. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.1.02; sites on affected versions should update now. Disclosed June 2026, reported by Thanh Điềm.
Vulnerability Overview
The WP Go Maps – Most Popular Map Plugin plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 10.1.01. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to create arbitrary records in plugin database tables (maps, markers, circles, polygons, polylines, rectangles, and point labels) by supplying a WPGMZA-namespaced CRUD-backed class name via the phpClass parameter. The namespace validation check (requiring the 'WPGMZA' prefix) does not prevent exploitation because classes such as WPGMZA\Map and WPGMZA\Marker satisfy it while still triggering an INSERT into the corresponding plugin table before the route rejects the request.
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, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Go Maps <= 10.1.01 carries this weakness at WPGMZA, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Go Maps the fix is 10.1.02: builds <= 10.1.01 are affected, anything from 10.1.02 onward is not.
Remediation
Update to version 10.1.02, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Go Maps 10.1.02 closes this, and updating the plugin is the step that ends it.
- Login Security
- 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-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 - 6.4WP Google Maps <= 6.3.14 Stored Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C