HomeWordPress vulnerabilitiesWP Maps
WP Maps vulnerabilities
WP Maps has 22 known vulnerabilities in this database. The most recent published record is dated 25 Sep 2026.
- Known vulnerabilities
- 22
- Active installs
- 60,000+
- Latest version
- 5.0.1
- Last updated
- 24 Sep 2026
- Most recent
- 25 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-13179 | Medium 6.4 | Up to 4.9.8 | Fixed in a later version (latest 5.0.1) | 12 d ago |
| File inclusion CVE-2026-13456 | High 7.5 | Up to 4.9.8 | Fixed in a later version (latest 5.0.1) | 12 d ago |
| Broken access control CVE-2026-18466 | Medium 5.4 | Before 4.9.8 | Fixed in 4.9.8 | 19 Aug 2026 |
| Path traversal CVE-2026-16263 | High 8.8 | Before 4.9.7 | Fixed in 4.9.7 | 7 Aug 2026 |
| Denial of service CVE-2026-16265 | Medium 6.5 | Before 4.9.7 | Fixed in 4.9.7 | 7 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-9594 | Medium 4.4 | Up to 4.9.4 | Fixed in a later version (latest 5.0.1) | 6 Jun 2026 |
| File inclusion CVE-2026-6381 | High 7.5 | Before 4.9.3 | Fixed in 4.9.3 | 18 May 2026 |
| SQL injection CVE-2026-2580 | High 7.5 | Up to 4.9.1 | Fixed in a later version (latest 5.0.1) | 23 Mar 2026 |
| SQL injection CVE-2026-3222 | High 7.5 | Up to 4.9.1 | Fixed in a later version (latest 5.0.1) | 11 Mar 2026 |
| PHP object injection CVE-2025-67535 | Medium 6.6 | Up to 4.8.6 | Fixed in a later version (latest 5.0.1) | 9 Dec 2025 |
| Cross-site scripting (XSS) CVE-2025-3504 | Medium 4.8 | Before 4.7.2 | Fixed in 4.7.2 | 1 May 2025 |
| Cross-site scripting (XSS) CVE-2025-3502 | Medium 4.8 | Before 4.7.2 | Fixed in 4.7.2 | 1 May 2025 |
| Cross-site scripting (XSS) CVE-2025-3503 | Medium 4.8 | Before 4.7.2 | Fixed in 4.7.2 | 1 May 2025 |
| SQL injection CVE-2024-2386 | High 8.8 | Up to 4.6.1 | Fixed in a later version (latest 5.0.1) | 29 Jun 2024 |
| Cross-site request forgery (CSRF) CVE-2023-28172 | Medium 5.4 | Up to 4.4.2 | Fixed in a later version (latest 5.0.1) | 12 Nov 2023 |
| Cross-site scripting (XSS) CVE-2023-23878 | Medium 5.9 | Before 4.4.0 | Fixed in 4.4.0 | 4 Apr 2023 |
| Cross-site request forgery (CSRF) CVE-2015-9307 | High 8.8 | Before 2.3.10 | Fixed in 2.3.10 | 14 Aug 2019 |
| Cross-site request forgery (CSRF) CVE-2015-9308 | High 8.8 | Before 2.3.10 | Fixed in 2.3.10 | 14 Aug 2019 |
| Cross-site request forgery (CSRF) CVE-2015-9309 | High 8.8 | Before 2.3.10 | Fixed in 2.3.10 | 14 Aug 2019 |
| Cross-site scripting (XSS) CVE-2015-9305 | Medium 6.1 | Before 2.3.7 | Fixed in 2.3.7 | 12 Aug 2019 |
| Cross-site scripting (XSS) CVE-2016-10878 | Medium 6.1 | Before 3.1.2 | Fixed in 3.1.2 | 12 Aug 2019 |
| Cross-site scripting (XSS) CVE-2018-0577 | Medium 5.4 | Before 4.0.4 | Fixed in 4.0.4 | 14 May 2018 |
Read the published descriptions
- CVE-2026-13179, 25 Sep 2026
- The WP Maps - Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shapes_values Parameter in all versions up to, and including, 4.9.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The fc-call-nonce nonce required by the endpoint is exposed to all frontend visitors who view a map page via window.wpgmp_local.nonce, enabling any authenticated subscriber to read the nonce and craft a valid request; additionally, the secondary _wpnonce check in the drawing handler can be bypassed by simply omitting the _wpnonce parameter from the request. CVE record
- CVE-2026-13456, 25 Sep 2026
- The WP Maps - Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.9.8 via the 'page' parameter parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. CVE record
- CVE-2026-18466, 19 Aug 2026
- The WP Maps WordPress plugin before 4.9.8 does not perform a capability check, nor validate a nonce, in one of its AJAX actions, allowing users with a Subscriber account to create an unlimited number of options in the database, each of which is loaded on every page request. CVE record
- CVE-2026-16263, 7 Aug 2026
- The WP Maps WordPress plugin before 4.9.7 does not perform a capability check in one of its AJAX actions and does not properly validate a user-controlled path before using it in a file inclusion, allowing users with a Subscriber account to include and execute arbitrary existing local PHP files on the server. CVE record
- CVE-2026-16265, 7 Aug 2026
- The WP Maps WordPress plugin before 4.9.7 does not perform a capability check in one of its AJAX actions and does not restrict the operation it dispatches, allowing users with a Subscriber account to trigger uncontrolled recursion that exhausts server resources, resulting in a Denial of Service. CVE record
- CVE-2026-9594, 6 Jun 2026
- The WP Maps - Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'location_messages' parameter in all versions up to, and including, 4.9.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker to hold the custom wpgmp_manage_location capability, which is granted to administrators by default but can be assigned to lower-privileged roles via the plugin's Permissions screen. CVE record
- CVE-2026-6381, 18 May 2026
- The WP Maps WordPress plugin before 4.9.3 does not properly sanitize a parameter before using it in a file path, allowing authenticated users to perform Local File Inclusion attacks. CVE record
- CVE-2026-2580, 23 Mar 2026
- The WP Maps - Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters plugin for WordPress is vulnerable to time-based SQL Injection via the ‘orderby’ parameter in all versions up to, and including, 4.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-3222, 11 Mar 2026
- The WP Maps plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'location_id' parameter in all versions up to, and including, 4.9.1. This is due to the plugin's database abstraction layer (`FlipperCode_Model_Base::is_column()`) treating user input wrapped in backticks as column names, bypassing the `esc_sql()` escaping function. Additionally, the `wpgmp_ajax_call` AJAX handler (registered for unauthenticated users via `wp_ajax_nopriv`) allows calling arbitrary class methods including `wpgmp_return_final_capability`, which passes the unsanitized `location_id` GET parameter directly to a database query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2025-67535, 9 Dec 2025
- Deserialization of Untrusted Data vulnerability in Flipper Code - WordPress Development Company WP Maps wp-google-map-plugin allows Object Injection.This issue affects WP Maps: from n/a through <= 4.8.6. CVE record
- CVE-2025-3504, 1 May 2025
- The WP Maps WordPress plugin before 4.7.2 does not sanitise and escape some of its Map settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2025-3502, 1 May 2025
- The WP Maps WordPress plugin before 4.7.2 does not sanitise and escape some of its Map settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2025-3503, 1 May 2025
- The WP Maps WordPress plugin before 4.7.2 does not sanitise and escape some of its Map settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2024-2386, 29 Jun 2024
- The WordPress Plugin for Google Maps - WP MAPS plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter of the 'put_wpgm' shortcode in all versions up to, and including, 4.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2023-28172, 12 Nov 2023
- Cross-Site Request Forgery (CSRF) vulnerability in flippercode WordPress Plugin for Google Maps - WP MAPS (formerly WP Google Map Plugin) plugin <= 4.4.2 versions. CVE record
- CVE-2023-23878, 4 Apr 2023
- Auth. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in flippercode WordPress Plugin for Google Maps - WP MAPS plugin <= 4.3.9 versions. CVE record
- CVE-2015-9307, 14 Aug 2019
- The wp-google-map-plugin plugin before 2.3.10 for WordPress has CSRF in the add/edit location feature. CVE record
- CVE-2015-9308, 14 Aug 2019
- The wp-google-map-plugin plugin before 2.3.10 for WordPress has CSRF in the add/edit map feature. CVE record
- CVE-2015-9309, 14 Aug 2019
- The wp-google-map-plugin plugin before 2.3.10 for WordPress has CSRF in the add/edit category feature. CVE record
- CVE-2015-9305, 12 Aug 2019
- The wp-google-map-plugin plugin before 2.3.7 for WordPress has XSS related to the add_query_arg() and remove_query_arg() functions. CVE record
- CVE-2016-10878, 12 Aug 2019
- The wp-google-map-plugin plugin before 3.1.2 for WordPress has XSS. CVE record
- CVE-2018-0577, 14 May 2018
- Cross-site scripting vulnerability in WP Google Map Plugin prior to version 4.0.4 for WordPress allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. CVE record
What to do if you run WP Maps
If you run WP Maps, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Maps vulnerabilities
Free. We email you when a new vulnerability is published for WP Maps, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.