WordPress plugin · wp-google-maps
Is WP Go Maps safe?
Safe on 10.1.10 or newer.
The current version, 10.1.10, is past every affected range on record (27 of 27 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 27
- High or critical
- 3
- Exploited
- none
- Current version
- 10.1.10
- Last updated
- Sep 28, 2026
- Active installs
- 300,000+
Every recorded flaw
- Sep 2, 2026Unauthenticated Denial of Service Attack in WP Go Maps <= 10.1.08 versions.CVE-2026-84780 · affects up to 10.1.08 · reported by PatchstackMedium 5.3
- Jul 31, 2026WP Go Maps: Does not properly sanitise and escape a parameter before using it in a SQL queryCVE-2026-15381 · fixed in 10.1.04 · reported by WPScanLow 3.7
- Jul 23, 2026Unauthenticated Broken Access Control in WP Go Maps <= 10.1.04 versions.CVE-2026-25466 · affects up to 10.1.04 · reported by PatchstackMedium 5.3
- Jun 19, 2026WP Go Maps – Most Popular Map: Authorization bypassCVE-2026-12238 · affects up to 10.1.01 · reported by WordfenceMedium 5.3
- Jun 15, 2026WP Go Maps: Does not perform any approval-state filtering on its public single-marker REST endpointCVE-2026-8386 · fixed in 10.0.10 · reported by WPScanMedium 5.3
- Jun 15, 2026WP Go Maps: Does not properly enforce the marker approval filter on the admin-ajax fallback for its datatables routeCVE-2026-8385 · fixed in 10.0.10 · reported by WPScanMedium 5.3
- Mar 17, 2026WP Go Maps (formerly WP Google Maps): Stored Cross-Site ScriptingCVE-2026-4268 · affects up to 10.0.05 · reported by WordfenceMedium 6.4
- Jan 24, 2026WP Go Maps (formerly WP Google Maps): Unauthorized modification of dataCVE-2026-0593 · affects up to 10.0.04 · reported by WordfenceMedium 5.3
- Nov 11, 2025WP Go Maps (formerly WP Google Maps): Does not sanitize user input provided via an AJAX actionCVE-2025-11307 · fixed in 9.0.48 · reported by WPScan2.0% oddsHigh 8.8
- Oct 18, 2025WP Go Maps (formerly WP Google Maps): Cache PoisoningCVE-2025-11703 · affects up to 9.0.48 · reported by WordfenceMedium 5.3
- Oct 8, 2025WP Go Maps (formerly WP Google Maps): Cross-Site Request Forgery (CSRF)CVE-2025-11166 · affects up to 9.0.46 · reported by WordfenceMedium 5.4
- Jan 27, 2025WP Go Maps: Cross-Site Request Forgery (CSRF)CVE-2025-24742 · affects up to 9.0.40 · reported by PatchstackMedium 4.3
- Jun 14, 2024WP Go Maps (formerly WP Google Maps): Stored Cross-Site ScriptingCVE-2024-5994 · affects up to 9.0.38 · reported by WordfenceMedium 6.4
- May 24, 2024WP Go Maps (formerly WP Google Maps): Stored Cross-Site ScriptingCVE-2024-3557 · affects up to 9.0.36 · reported by WordfenceMedium 6.4
- Apr 9, 2024WP Go Maps (formerly WP Google Maps): Unauthenticated API key disclosureCVE-2023-6777 · affects up to 9.0.34 · reported by WordfenceMedium 5.3
- Mar 27, 2024WP Go Maps: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2024-29931 · affects up to 9.0.29 · reported by PatchstackHigh 7.1
- Mar 12, 2024WP Go Maps (formerly WP Google Maps): Stored Cross-Site ScriptingCVE-2024-1582 · affects up to 9.0.32 · reported by WordfenceMedium 6.4
- Mar 12, 2024WP Go Maps: Stored Cross-Site ScriptingCVE-2023-4839 · affects up to 9.0.32 · reported by WordfenceMedium 4.4
- Jan 24, 2024WP Go Maps (formerly WP Google Maps): Reflected Cross-Site ScriptingCVE-2023-6697 · affects up to 9.0.28 · reported by Wordfence1.0% oddsMedium 6.1
- Jan 8, 2024WP Go Maps (formerly WP Google Maps): Does not properly protect most of its REST API routesCVE-2023-6627 · fixed in 9.0.28 · reported by WPScanMedium 6.1
- Mar 14, 2023WP Go Maps: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVE-2022-47595 · affects up to 9.0.15 · reported by PatchstackMedium 4.9
- Sep 9, 2021Multiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in WordPress WP Google Maps plugin (versions <= 8.1.12).CVE-2021-36870 · affects up to 8.1.12 · reported by PatchstackMedium 5.5
- Jun 21, 2021WP Google Maps: Did not sanitiseCVE-2021-24383 · fixed in 8.1.12 · reported by WPScan2.5% oddsMedium 5.4
- Aug 9, 2019The WP Google Maps plugin before 7.11.35 for WordPress allows XSS via the wp-admin/ rectangle_name or rectangle_opacity parameter.CVE-2019-14792 · fixed in 7.11.35 · reported by MITRE1.1% oddsMedium 5.4
- Apr 2, 2019In the wp-google-maps plugin before 7.11.18 for WordPress, includes/class.rest-api.php in the REST API does not sanitize field names before a SELECT statement.CVE-2019-10692 · fixed in 7.11.18 · reported by MITRE77% oddsCritical 9.8
- Mar 21, 2019The wp-google-maps plugin before 7.10.43 for WordPress has XSS via the wp-admin/admin.php PATH_INFO.CVE-2019-9912 · fixed in 7.10.43 · reported by MITRE3.1% oddsMedium 6.1
- Oct 22, 2014Multiple cross-site scripting (XSS) vulnerabilities in the WP Google Maps plugin before 6.0.27 for WordPress allow remote attackers to inject arbitrary web scriCVE-2014-7182 · fixed in 6.0.27 · reported by MITRE2.5% oddsMedium 4.3
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Get in touch
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
Not ready to talk yet? Run the free website check and see what Google sees.