WordPress plugin · Updated daily · Source: Wordfence Intelligence

WP Go Maps vulnerabilities: affected versions and fixes

WP Go Maps has 300,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

WP Go Maps at a glance

  • 31 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Nov 17, 2026.
  • Ranked #198 by popularity on WordPress.org (300,000+ active installs).
  • The latest version is 10.2.03 (released Nov 20, 2026). The most recent security fix shipped in 10.2.00.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your WP Go Maps version

Enter the WP Go Maps version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “WP Go Maps”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WP Go Maps”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (10.2.03). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known WP Go Maps vulnerabilities (latest 25 of 31)

  • WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator <= 10.1.12 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-129049

    Affected versions: ≤ 10.1.12

    Fixed in: 10.2.00

    Severity: Medium 6.4 · Disclosed Nov 17, 2026

  • WP Go Maps – Google Map, OpenStreetMap, Leaflet & Store Locator <= 10.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-125824

    Affected versions: ≤ 10.1.10

    Fixed in: 10.1.11

    Severity: Medium 6.4 · Disclosed Nov 13, 2026

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

    Other weakness · CVE-2026-84780

    Affected versions: ≤ 10.1.08

    Fixed in: 10.1.09

    Severity: High 7.5 · Disclosed Sep 2, 2026

  • WP Go Maps – Google Map, OpenStreetMap, Leaflet Map < 10.1.04 - Unauthenticated SQL Injection

    SQL injection · CVE-2026-15381

    Affected versions: < 10.1.04

    Fixed in: 10.1.04

    Severity: High 7.5 · Disclosed Aug 4, 2026

  • WP Go Maps – Google Map, OpenStreetMap, Leaflet Map <= 10.1.05 - Missing Authorization

    Missing authorization · CVE-2026-25466

    Affected versions: ≤ 10.1.05

    Fixed in: 10.1.06

    Severity: Medium 5.3 · Disclosed Jul 22, 2026

  • WP Go Maps <= 10.1.01 - Unauthenticated Arbitrary Record Creation

    Missing authorization · CVE-2026-12238

    Affected versions: ≤ 10.1.01

    Fixed in: 10.1.02

    Severity: Medium 5.3 · Disclosed Jun 19, 2026

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

    Information disclosure · CVE-2026-8385

    Affected versions: ≤ 10.0.09

    Fixed in: 10.0.10

    Severity: Medium 5.3 · Disclosed Jun 5, 2026

  • Go Maps <= 10.0.9 - Unauthenticated Information Exposure

    Information disclosure · CVE-2026-8386

    Affected versions: ≤ 10.0.9

    Fixed in: 10.0.10

    Severity: Medium 5.3 · Disclosed May 25, 2026

  • 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

    Cross-site scripting (XSS) · CVE-2026-4268

    Affected versions: ≤ 10.0.05

    Fixed in: 10.0.06

    Severity: Medium 6.4 · Disclosed Mar 17, 2026

  • WP Go Maps (formerly WP Google Maps) <= 10.0.04 - Missing Authorization to Authenticated (Subscriber+) Map Engine Setting Modification

    Missing authorization · CVE-2026-0593

    Affected versions: ≤ 10.0.04

    Fixed in: 10.0.05

    Severity: Medium 5.3 · Disclosed Jan 24, 2026

  • Google Maps <= 9.0.47 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-11307

    Affected versions: ≤ 9.0.47

    Fixed in: 9.0.48

    Severity: High 7.2 · Disclosed Oct 21, 2025

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

    Other weakness · CVE-2025-11703

    Affected versions: ≤ 9.0.48

    Fixed in: 9.0.49

    Severity: Medium 5.3 · Disclosed Oct 17, 2025

  • WP Go Maps (formerly WP Google Maps) <= 9.0.46 - Cross-Site Request Forgery to Plugin Settings Update

    Cross-site request forgery (CSRF) · CVE-2025-11166

    Affected versions: ≤ 9.0.46

    Fixed in: 9.0.47

    Severity: Medium 5.4 · Disclosed Oct 8, 2025

  • WP Go Maps <= 9.0.40 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2025-24742

    Affected versions: ≤ 9.0.40

    Fixed in: 9.0.41

    Severity: Medium 4.3 · Disclosed Jan 24, 2025

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

    Cross-site scripting (XSS) · CVE-2024-5994

    Affected versions: ≤ 9.0.38

    Fixed in: 9.0.39

    Severity: Medium 6.4 · Disclosed Jun 13, 2024

  • WP Go Maps (formerly WP Google Maps) <= 9.0.36 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2024-3557

    Affected versions: ≤ 9.0.36

    Fixed in: 9.0.37

    Severity: Medium 6.4 · Disclosed May 23, 2024

  • WP Google Maps <= 9.0.29 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-29931

    Affected versions: ≤ 9.0.29

    Fixed in: 9.0.30

    Severity: Medium 6.1 · Disclosed Mar 25, 2024

  • WP Go Maps (formerly WP Google Maps) <= 9.0.34 - Information Exposure to Potential Denial of Service

    Information disclosure · CVE-2023-6777

    Affected versions: ≤ 9.0.34

    Fixed in: 9.0.35

    Severity: Medium 5.3 · Disclosed Mar 18, 2024

  • WP Go Maps (formerly WP Google Maps) <= 9.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2024-1582

    Affected versions: ≤ 9.0.32

    Fixed in: 9.0.33

    Severity: Medium 6.4 · Disclosed Mar 12, 2024

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

    Cross-site scripting (XSS) · CVE-2023-4839

    Affected versions: ≤ 9.0.32

    Fixed in: 9.0.33

    Severity: Medium 4.4 · Disclosed Mar 12, 2024

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

    Cross-site scripting (XSS) · CVE-2023-6697

    Affected versions: ≤ 9.0.28

    Fixed in: 9.0.29

    Severity: Medium 6.1 · Disclosed Jan 23, 2024

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

    Cross-site scripting (XSS) · CVE-2023-6627

    Affected versions: ≤ 9.0.27

    Fixed in: 9.0.28

    Severity: Medium 6.1 · Disclosed Dec 18, 2023

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

    Arbitrary file read or deletion · CVE-2022-47595

    Affected versions: ≤ 9.0.15

    Fixed in: 9.0.16

    Severity: Medium 4.9 · Disclosed Jan 20, 2023

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

    Cross-site scripting (XSS) · CVE-2021-36870

    Affected versions: < 8.1.13

    Fixed in: 8.1.13

    Severity: Medium 5.5 · Disclosed Sep 8, 2021

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

    Cross-site scripting (XSS) · CVE-2021-24383

    Affected versions: < 8.1.12

    Fixed in: 8.1.12

    Severity: Medium 5.4 · Disclosed Jun 7, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 17, 2026.

Most common weaknesses in WP Go Maps

Cross-site scripting (XSS)

17 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

3 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Information disclosure

3 issues

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is WP Go Maps safe to use?

WP Go Maps is a well-known plugin with 300,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (10.2.03) and turn on automatic updates.

How do I find which version of WP Go Maps my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesWP Go Maps on WordPress.org