Skip to main content
WordPress plugin recordReviewed

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.

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.

  1. 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)
    Affected versions
    • All versions up to and including 10.1.12

    Patched versions: 10.2.00

    Update to at least version 10.2.00.

  2. 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)
    Affected versions
    • All versions up to and including 10.1.10

    Patched versions: 10.1.11

    Update to at least version 10.1.11.

  3. WP Go Maps - Google Map, OpenStreetMap, Leaflet Map <= 10.1.08 - Unauthenticated Denial of Service

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 10.1.08

    Patched versions: 10.1.09

    Update to at least version 10.1.09.

  4. WP Go Maps - Google Map, OpenStreetMap, Leaflet Map < 10.1.04 - Unauthenticated SQL Injection

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions before 10.1.04

    Patched versions: 10.1.04

    Update to at least version 10.1.04.

  5. WP Go Maps - Google Map, OpenStreetMap, Leaflet Map <= 10.1.05 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    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 records
  1. WP Go Maps <= 10.1.01 - Unauthenticated Arbitrary Record Creation

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 10.1.01

    Patched versions: 10.1.02

    Update to at least version 10.1.02.

  2. WP Go Maps < 10.0.10 - Unauthenticated Sensitive Information Disclosure via Datatables AJAX Fallback

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 10.0.09

    Patched versions: 10.0.10

    Update to at least version 10.0.10.

  3. Go Maps <= 10.0.9 - Unauthenticated Information Exposure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 10.0.9

    Patched versions: 10.0.10

    Update to at least version 10.0.10.

  4. 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)
    Affected versions
    • All versions up to and including 10.0.05

    Patched versions: 10.0.06

    Update to at least version 10.0.06.

  5. 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)
    Affected versions
    • All versions up to and including 10.0.04

    Patched versions: 10.0.05

    Update to at least version 10.0.05.

  6. Google Maps <= 9.0.47 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 9.0.47

    Patched versions: 9.0.48

    Update to at least version 9.0.48.

  7. WP Go Maps (formerly WP Google Maps) <= 9.0.48 - Unauthenticated Cache Poisoning

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 9.0.48

    Patched versions: 9.0.49

    Update to at least version 9.0.49.

  8. 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)
    Affected versions
    • All versions up to and including 9.0.46

    Patched versions: 9.0.47

    Update to at least version 9.0.47.

  9. WP Go Maps <= 9.0.40 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 9.0.40

    Patched versions: 9.0.41

    Update to at least version 9.0.41.

  10. WP Go Maps (formerly WP Google Maps) <= 9.0.38 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 9.0.38

    Patched versions: 9.0.39

    Update to at least version 9.0.39.

  11. 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)
    Affected versions
    • All versions up to and including 9.0.36

    Patched versions: 9.0.37

    Update to at least version 9.0.37.

  12. WP Google Maps <= 9.0.29 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 9.0.29

    Patched versions: 9.0.30

    Update to at least version 9.0.30.

  13. 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)
    Affected versions
    • All versions up to and including 9.0.34

    Patched versions: 9.0.35

    Update to at least version 9.0.35.

  14. WP Go Maps <= 9.0.32 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.4)
    Affected versions
    • All versions up to and including 9.0.32

    Patched versions: 9.0.33

    Update to at least version 9.0.33.

  15. 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)
    Affected versions
    • All versions up to and including 9.0.32

    Patched versions: 9.0.33

    Update to at least version 9.0.33.

  16. WP Go Maps (formerly WP Google Maps) <= 9.0.28 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 9.0.28

    Patched versions: 9.0.29

    Update to at least version 9.0.29.

  17. WP Google Maps <= 9.0.27 - Unauthenticated Stored Cross-Site Scripting via REST API

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 9.0.27

    Patched versions: 9.0.28

    Update to at least version 9.0.28.

  18. WP Go Maps <= 9.0.15 - Authenticated (Admin+) Directory Traversal

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.9)
    Affected versions
    • All versions up to and including 9.0.15

    Patched versions: 9.0.16

    Update to at least version 9.0.16.

  19. WP Google Maps <= 8.1.12 - Authenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions before 8.1.13

    Patched versions: 8.1.13

    Update to at least version 8.1.13.

  20. WP Google Maps <= 8.1.11 - Authenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions before 8.1.12

    Patched versions: 8.1.12

    Update to at least version 8.1.12.

  21. WP Go Maps (formerly WP Google Maps) <= 7.11.17 - SQL Injection

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 7.11.17

    Patched versions: 7.11.18

    Update to at least version 7.11.18.

  22. WP Google Maps <= 7.11.34 - Cross-Site Request Forgery to Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions before 7.11.35

    Patched versions: 7.11.35

    Update to at least version 7.11.35.

  23. 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.

  24. WP Google Maps < 7.10.43 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 7.10.41

    Patched versions: 7.10.43

    Update to at least version 7.10.43.

  25. 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.

  26. WP Google Maps <= 6.0.26 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    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".

Installed version and update status of WP Go Maps and its add-ons

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. 1 min read

Who can open the map editor

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. 1 min read

Stored map content shown to visitors

The vendor's marker page lists each map's markers at WP Go MAPS > Maps (edit your chosen map) > Markers. 1 min read

Map engine and API key handling

Note the map engine, which the listing says is switched from Maps > Settings. 1 min read

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 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