WordPress security changelog
MEDIUM CVE-2026-12238 Deferred

WP Go Maps – Google Map, OpenStreetMap, Leaflet Map: A security weakness

WP Go Maps – Google Map, OpenStreetMap, Leaflet Map is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 10.1.01.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
Plugin slug
wp-google-maps
Affected
<= 10.1.01
Safe version
> 10.1.01
Published
Jun 19, 2026
Weakness
CWE-862 — Missing Authorization

This CVE was published Jun 19, 2026 and is one of 12 known issues for this plugin.

Update, patch or deactivate.

Update WP Go Maps – Google Map, OpenStreetMap, Leaflet Map to a release after 10.1.01, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Primary and upstream sources