WP Go Maps vulnerability records, read against its map editor, markers and API key
WP Go Maps was formerly WP Google Maps, and its records use both names, so the version fields decide which apply.
The map editor's access level, marker content, visitor submissions and the Google Maps API key restriction are the settings to read alongside them.
On this page
WP Go Maps vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 31 records for WP Go Maps. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 10.2.00
Worked out from data retrieved on .
Every affected range listed in this source for WP Go Maps ends before version 10.2.00.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
WP Go Maps - Google Map, OpenStreetMap, Leaflet & Store Locator <= 10.1.12 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-129049
Affected versions- All versions up to and including 10.1.12
Patched versions: 10.2.00
Update to at least version 10.2.00.
WP Go Maps - Google Map, OpenStreetMap, Leaflet & Store Locator <= 10.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-125824
Affected versions- All versions up to and including 10.1.10
Patched versions: 10.1.11
Update to at least version 10.1.11.
WP Go Maps - Google Map, OpenStreetMap, Leaflet Map <= 10.1.08 - Unauthenticated Denial of Service
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2026-84780
Affected versions- All versions up to and including 10.1.08
Patched versions: 10.1.09
Update to at least version 10.1.09.
WP Go Maps - Google Map, OpenStreetMap, Leaflet Map < 10.1.04 - Unauthenticated SQL Injection
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2026-15381
Affected versions- All versions before 10.1.04
Patched versions: 10.1.04
Update to at least version 10.1.04.
WP Go Maps - Google Map, OpenStreetMap, Leaflet Map <= 10.1.05 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-25466
Affected versions- All versions up to and including 10.1.05
Patched versions: 10.1.06
Update to at least version 10.1.06.
Show 26 older recordsHide the older records
WP Go Maps <= 10.1.01 - Unauthenticated Arbitrary Record Creation
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-12238
Affected versions- All versions up to and including 10.1.01
Patched versions: 10.1.02
Update to at least version 10.1.02.
WP Go Maps < 10.0.10 - Unauthenticated Sensitive Information Disclosure via Datatables AJAX Fallback
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-8385
Affected versions- All versions up to and including 10.0.09
Patched versions: 10.0.10
Update to at least version 10.0.10.
Go Maps <= 10.0.9 - Unauthenticated Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-8386
Affected versions- All versions up to and including 10.0.9
Patched versions: 10.0.10
Update to at least version 10.0.10.
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
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-4268
Affected versions- All versions up to and including 10.0.05
Patched versions: 10.0.06
Update to at least version 10.0.06.
WP Go Maps (formerly WP Google Maps) <= 10.0.04 - Missing Authorization to Authenticated (Subscriber+) Map Engine Setting Modification
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-0593
Affected versions- All versions up to and including 10.0.04
Patched versions: 10.0.05
Update to at least version 10.0.05.
Google Maps <= 9.0.47 - Unauthenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2025-11307
Affected versions- All versions up to and including 9.0.47
Patched versions: 9.0.48
Update to at least version 9.0.48.
WP Go Maps (formerly WP Google Maps) <= 9.0.48 - Unauthenticated Cache Poisoning
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2025-11703
Affected versions- All versions up to and including 9.0.48
Patched versions: 9.0.49
Update to at least version 9.0.49.
WP Go Maps (formerly WP Google Maps) <= 9.0.46 - Cross-Site Request Forgery to Plugin Settings Update
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
- CVE:
- CVE-2025-11166
Affected versions- All versions up to and including 9.0.46
Patched versions: 9.0.47
Update to at least version 9.0.47.
WP Go Maps <= 9.0.40 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2025-24742
Affected versions- All versions up to and including 9.0.40
Patched versions: 9.0.41
Update to at least version 9.0.41.
WP Go Maps (formerly WP Google Maps) <= 9.0.38 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-5994
Affected versions- All versions up to and including 9.0.38
Patched versions: 9.0.39
Update to at least version 9.0.39.
WP Go Maps (formerly WP Google Maps) <= 9.0.36 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-3557
Affected versions- All versions up to and including 9.0.36
Patched versions: 9.0.37
Update to at least version 9.0.37.
WP Google Maps <= 9.0.29 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2024-29931
Affected versions- All versions up to and including 9.0.29
Patched versions: 9.0.30
Update to at least version 9.0.30.
WP Go Maps (formerly WP Google Maps) <= 9.0.34 - Information Exposure to Potential Denial of Service
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2023-6777
Affected versions- All versions up to and including 9.0.34
Patched versions: 9.0.35
Update to at least version 9.0.35.
WP Go Maps <= 9.0.32 - Authenticated (Administrator+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.4)
- CVE:
- CVE-2023-4839
Affected versions- All versions up to and including 9.0.32
Patched versions: 9.0.33
Update to at least version 9.0.33.
WP Go Maps (formerly WP Google Maps) <= 9.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-1582
Affected versions- All versions up to and including 9.0.32
Patched versions: 9.0.33
Update to at least version 9.0.33.
WP Go Maps (formerly WP Google Maps) <= 9.0.28 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2023-6697
Affected versions- All versions up to and including 9.0.28
Patched versions: 9.0.29
Update to at least version 9.0.29.
WP Google Maps <= 9.0.27 - Unauthenticated Stored Cross-Site Scripting via REST API
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2023-6627
Affected versions- All versions up to and including 9.0.27
Patched versions: 9.0.28
Update to at least version 9.0.28.
WP Go Maps <= 9.0.15 - Authenticated (Admin+) Directory Traversal
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.9)
- CVE:
- CVE-2022-47595
Affected versions- All versions up to and including 9.0.15
Patched versions: 9.0.16
Update to at least version 9.0.16.
WP Google Maps <= 8.1.12 - Authenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.5)
- CVE:
- CVE-2021-36870
Affected versions- All versions before 8.1.13
Patched versions: 8.1.13
Update to at least version 8.1.13.
WP Google Maps <= 8.1.11 - Authenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
- CVE:
- CVE-2021-24383
Affected versions- All versions before 8.1.12
Patched versions: 8.1.12
Update to at least version 8.1.12.
WP Go Maps (formerly WP Google Maps) <= 7.11.17 - SQL Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2019-10692
Affected versions- All versions up to and including 7.11.17
Patched versions: 7.11.18
Update to at least version 7.11.18.
WP Google Maps <= 7.11.34 - Cross-Site Request Forgery to Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2019-14792
Affected versions- All versions before 7.11.35
Patched versions: 7.11.35
Update to at least version 7.11.35.
WP Google Maps <= 7.11.27 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
Affected versions- All versions before 7.11.28
Patched versions: 7.11.28
Update to at least version 7.11.28.
WP Google Maps < 7.10.43 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2019-9912
Affected versions- All versions up to and including 7.10.41
Patched versions: 7.10.43
Update to at least version 7.10.43.
WP Google Maps <= 6.3.14 - Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
Affected versions- All versions up to and including 6.3.14
Patched versions: 6.3.15
Update to at least version 6.3.15.
WP Google Maps <= 6.0.26 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2014-7182
Affected versions- All versions before 6.0.27
Patched versions: 6.0.27
Update to at least version 6.0.27.
Check WP Go Maps on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What WP Go Maps stores, and who can change it
WP Go Maps is listed on WordPress.org by WPGMaps, with the line "Formerly WP Google Maps." Its listing describes maps with markers, polygons, polylines and a store locator, added to posts and pages with the supplied shortcode, a map block or a widget, and says a Google API key is needed only if you choose Google Maps as the map engine.
Content reaches it in four places: the map editor, where the vendor's marker page says a Pro marker's Description accepts HTML; the plugin's settings, whose files carry API key fields and a "Custom Scripts" heading over CSS and JavaScript fields; posts and pages carrying the wpgmza shortcode; and, with the Pro and Visitor Generated Markers add-ons, markers that visitors create, as the vendor's visitor marker page describes.
What the WP Go Maps records name, and the access each title states
Cross-Site Scripting, stored and reflected, recurs through the titles, and so do Cross-Site Request Forgery, SQL Injection and Information Exposure.
Access wording in the titles includes "Unauthenticated", "(Subscriber+)", "(Contributor+)" and "(Administrator+)". Titles also open with different names, among them "WP Google Maps", "Google Maps", "Go Maps" and "WP Go Maps (formerly WP Google Maps)". All are records the source data files under the wp-google-maps slug, so match each on its version fields, whatever name it opens with.
- CVE-2024-1582 and CVE-2024-3557 share a title ending "Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode". CVE-2024-1582 lists all versions up to and including 9.0.32 and patched versions 9.0.33; CVE-2024-3557 lists all versions up to and including 9.0.36 and patched versions 9.0.37.
- CVE-2026-0593, title ending "(Subscriber+) Map Engine Setting Modification": all versions up to and including 10.0.04; patched versions field 10.0.05.
- CVE-2026-15381, title ending "Unauthenticated SQL Injection": all versions before 10.1.04; patched versions field 10.1.04.
- CVE-2026-25466: all versions up to and including 10.1.05; patched versions field 10.1.06.
- CVE-2019-9912, title beginning "WP Google Maps < 7.10.43": all versions up to and including 7.10.41; patched versions field 7.10.43.
Why the fields decide, not the title
The title of CVE-2019-9912 carries "< 7.10.43", but its affected range stops at 7.10.41: the fields say nothing about the versions between the two, so for that record the patched version is the one to reach. Match on the affected range and patched versions field, not on the version a title carries.
Running the WP Go Maps checks without changing anything
Sign in as an administrator on a site you are authorised to review, and treat every WP Go Maps screen as read-only.
The listing's changelog says a first time usage flow opens the marker creator once for new users, that in the Atlas Major editor form changes are persisted shortly after a change, and that a map preview generates a draft page. So change no field and leave the preview alone, along with the buttons the settings files place under "Danger Zone", among them "Complete Reset".
Note the version number that the Plugins screen gives in the Description column of the WP Go Maps row, and the day you read it. The vendor's installing page says the Pro version is an Add-on to the Basic version, and that the Gold Add-on and the Visitor Generated Markers Add-on require the Pro Add-on.
Record every WP Go Maps row. The same page installs Pro by uploading a file named wp-google-maps-pro.zip, and WordPress's Plugins screen documentation says a plugin installed from a ZIP file shows an update notice only if its author includes a built-in updater.
The plugin's WordPress.org listing has a Changelog section in which some lines carry the words "Security issue"; read it as well as the update guidance at the top of the history.
One of the plugin's settings files labels this setting "Lowest Access Level" and another "Lowest level of access to the map editor", with the choices Admin, Editor, Author, Contributor and Subscriber. Write down its value, then count the accounts in that role and in each role above it, using the role filter links on the Users screen.
The note beside the setting reads: "Granting lower level users access to the settings/editor will allow them to manage custom scripts (JavaScript), which could be abused, please exercise caution and consider this carefully." Where the Visitor Generated Markers add-on is installed, the vendor's page also puts an "Allowed Users" dropdown in each map's Visitor Generated Markers settings, with Everyone for public visitors or Registered users; record it for each map.
The vendor's marker page lists each map's markers at WP Go MAPS > Maps (edit your chosen map) > Markers. With Pro, the fields include Description, which accepts HTML, Link URL, which lets visitors open a web page from the InfoWindow, and "Display on front end", which defaults to Yes. Note markup nobody expected and links to domains the business does not control, and leave "Save Marker" alone.
For visitor markers, the vendor's page lists global settings at WP Go Maps > Settings > Visitor Generated Markers, among them "Auto Approve" and "Remove HTML". It says that when "Auto Approve" is enabled, all new visitor generated markers are automatically approved and will be displayed on the map, and that enabling "Remove HTML" will strip all HTML tags in descriptions and titles; write down both.
Then note whether the "Custom Scripts" CSS and JavaScript fields hold code, and list the posts and pages carrying the wpgmza shortcode with each author's role.
Note the map engine, which the listing says is switched from Maps > Settings. The listing's FAQ also places the API key in Maps > Settings, while the vendor's API key page gives WP GO Maps -> Settings -> Advanced Settings -> Google Maps API Key.
Record whether a key is present and leave its value out of your notes. That page offers two ways to obtain a key: the vendor's Cloud API Key, or one created in the Google Maps Platform, and it says that if you are already logged into a Google account, the new key will be created against that account. Note which, and who holds that account.
The vendor's protecting page sets the restriction in the Google API Manager: Credentials, then Edit API key, then "Set an application restriction" with "Websites" selected. Google's security guidance says best practice is to always restrict API keys with one type of application restriction and one or more API restrictions. Ask the account holder to read out both restrictions without saving.
Map settings that a WP Go Maps version number cannot reveal
A WP Go Maps version inside one of the affected ranges ties this copy to a known record, and stops there.
Whether the flaw was used is a separate question, and so are the settings this page has you read: a "Lowest Access Level" below Admin, visitor markers open to Everyone with "Auto Approve" on, code under "Custom Scripts", or a Google key with no website restriction. A WordPress security audit uses its own test account for each role.
With the editor account it saves script and checks whether that script runs when an administrator opens the page, and it calls plugin, theme, user and settings requests directly as an editor to confirm they are refused.
Frequently asked questions
The WordPress.org listing says "Formerly WP Google Maps.", and its address uses the wp-google-maps slug. Records in the history are titled under both names, and some under "Google Maps" or "Go Maps".
The records here are the ones the source data files under the wp-google-maps slug, and being filed there does not settle whether a record also applies to the Pro Add-on, Gold or Visitor Generated Markers. The vendor's installing page says Pro is an Add-on to the Basic version, which must be installed and activated for Pro to run, and that Gold and Visitor Generated Markers require Pro. Keep each add-on row's version with your notes, and put the coverage question for those add-ons to the vendor.
The vendor's page says you can allow visitors to create markers if you have purchased both the Visitor Generated Markers and Pro Add-ons, and that once a map's "Allow Submissions" option is enabled, the form is displayed on the front end. Its "Allowed Users" dropdown offers Everyone or Registered users.
Not necessarily. CVE-2026-15381 lists 10.1.04 in its patched versions field, while CVE-2026-25466 covers all versions up to and including 10.1.05, so a copy at 10.1.04 has left the first range and is still inside the second. Compare the installed version with every affected range in the history, and with the update guidance at the top of it.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 29 of the 31 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- WP Go Maps - Google Map, OpenStreetMap, Leaflet & Store Locator <= 10.1.12 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2026-129049)
- WP Go Maps - Google Map, OpenStreetMap, Leaflet & Store Locator <= 10.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2026-125824)
- WP Go Maps - Google Map, OpenStreetMap, Leaflet Map <= 10.1.08 - Unauthenticated Denial of Service (CVE-2026-84780)
- WP Go Maps - Google Map, OpenStreetMap, Leaflet Map < 10.1.04 - Unauthenticated SQL Injection (CVE-2026-15381)
- WP Go Maps - Google Map, OpenStreetMap, Leaflet Map <= 10.1.05 - Missing Authorization (CVE-2026-25466)
- WP Go Maps <= 10.1.01 - Unauthenticated Arbitrary Record Creation (CVE-2026-12238)
- WP Go Maps < 10.0.10 - Unauthenticated Sensitive Information Disclosure via Datatables AJAX Fallback (CVE-2026-8385)
- Go Maps <= 10.0.9 - Unauthenticated Information Exposure (CVE-2026-8386)
- 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 (CVE-2026-4268)
- WP Go Maps (formerly WP Google Maps) <= 10.0.04 - Missing Authorization to Authenticated (Subscriber+) Map Engine Setting Modification (CVE-2026-0593)
- Google Maps <= 9.0.47 - Unauthenticated Stored Cross-Site Scripting (CVE-2025-11307)
- WP Go Maps (formerly WP Google Maps) <= 9.0.48 - Unauthenticated Cache Poisoning (CVE-2025-11703)
- WP Go Maps (formerly WP Google Maps) <= 9.0.46 - Cross-Site Request Forgery to Plugin Settings Update (CVE-2025-11166)
- WP Go Maps <= 9.0.40 - Cross-Site Request Forgery (CVE-2025-24742)
- WP Go Maps (formerly WP Google Maps) <= 9.0.38 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2024-5994)
- WP Go Maps (formerly WP Google Maps) <= 9.0.36 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (CVE-2024-3557)
- WP Google Maps <= 9.0.29 - Reflected Cross-Site Scripting (CVE-2024-29931)
- WP Go Maps (formerly WP Google Maps) <= 9.0.34 - Information Exposure to Potential Denial of Service (CVE-2023-6777)
- WP Go Maps <= 9.0.32 - Authenticated (Administrator+) Stored Cross-Site Scripting (CVE-2023-4839)
- WP Go Maps (formerly WP Google Maps) <= 9.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (CVE-2024-1582)
- WP Go Maps (formerly WP Google Maps) <= 9.0.28 - Reflected Cross-Site Scripting (CVE-2023-6697)
- WP Google Maps <= 9.0.27 - Unauthenticated Stored Cross-Site Scripting via REST API (CVE-2023-6627)
- WP Go Maps <= 9.0.15 - Authenticated (Admin+) Directory Traversal (CVE-2022-47595)
- WP Google Maps <= 8.1.12 - Authenticated Stored Cross-Site Scripting (CVE-2021-36870)
- WP Google Maps <= 8.1.11 - Authenticated Stored Cross-Site Scripting (CVE-2021-24383)
- WP Go Maps (formerly WP Google Maps) <= 7.11.17 - SQL Injection (CVE-2019-10692)
- WP Google Maps <= 7.11.34 - Cross-Site Request Forgery to Cross-Site Scripting (CVE-2019-14792)
- WP Google Maps <= 7.11.27 - Cross-Site Request Forgery
- WP Google Maps < 7.10.43 - Reflected Cross-Site Scripting (CVE-2019-9912)
- WP Google Maps <= 6.3.14 - Stored Cross-Site Scripting
- WP Google Maps <= 6.0.26 - Reflected Cross-Site Scripting (CVE-2014-7182)