Basic Google Maps Placemarks Security & Risk Analysis

wordpress.org/plugins/basic-google-maps-placemarks

Embeds a Google Map into your site and lets you add map markers with custom icons and information windows.

3K active installs v1.10.7 PHP + WP 3.1+ Updated Nov 28, 2017
geocodegoogle-mapsmapmarkerplacemark
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Basic Google Maps Placemarks Safe to Use in 2026?

Generally Safe

Score 85/100

Basic Google Maps Placemarks has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The plugin 'basic-google-maps-placemarks' version 1.10.7 exhibits a generally good security posture based on the static analysis and vulnerability history. The plugin has no known vulnerabilities (CVEs) and demonstrates a commitment to security by implementing capability checks on its entry points and performing external HTTP requests with caution. The attack surface is minimal, with no unprotected AJAX handlers or REST API routes.

However, there are areas for improvement. The analysis reveals that 0% of SQL queries use prepared statements, which is a significant concern. While there are no critical or high-severity taint flows identified, the presence of 4 flows with unsanitized paths indicates a potential risk that could be exploited if malicious data is introduced. Furthermore, the output escaping is only at 52%, meaning a substantial portion of the plugin's output is not properly sanitized, posing a risk of Cross-Site Scripting (XSS) vulnerabilities.

Overall, the plugin's lack of historical vulnerabilities is a positive sign. However, the identified coding practices, particularly the absence of prepared statements for SQL and the moderate output escaping, represent tangible risks that should be addressed to further harden its security.

Key Concerns

  • SQL queries not using prepared statements
  • Low percentage of properly escaped output
  • Unsanitized paths in taint flows
Vulnerabilities
None known

Basic Google Maps Placemarks Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Basic Google Maps Placemarks Code Analysis

Dangerous Functions
0
Raw SQL Queries
1
0 prepared
Unescaped Output
24
26 escaped
Nonce Checks
0
Capability Checks
2
File Operations
0
External Requests
2
Bundled Libraries
0

SQL Query Safety

0% prepared1 total queries

Output Escaping

52% escaped50 total outputs
Data Flows
4 unsanitized

Data Flow Analysis

4 flows4 with unsanitized paths
saveCustomFields (core.php:855)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Basic Google Maps Placemarks Attack Surface

Entry Points2
Unprotected0

Shortcodes 2

[bgmp-map] core.php:49
[bgmp-list] core.php:50
WordPress Hooks 20
actionadmin_noticesbasic-google-maps-placemarks.php:92
actioninitcore.php:33
actioninitcore.php:34
actioninitcore.php:35
actioninitcore.php:36
actionafter_setup_themecore.php:37
actionadmin_initcore.php:38
actionwpcore.php:39
actionadmin_enqueue_scriptscore.php:40
actionwp_headcore.php:41
actionadmin_noticescore.php:42
actionsave_postcore.php:43
actionwpmu_new_blogcore.php:44
actionshutdowncore.php:45
filterparse_querycore.php:47
actioninitsettings.php:26
actioninitsettings.php:27
actionadmin_menusettings.php:28
actionadmin_initsettings.php:29
filterplugin_action_links_basic-google-maps-placemarks/basic-google-maps-placemarks.phpsettings.php:31
Maintenance & Trust

Basic Google Maps Placemarks Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedNov 28, 2017
PHP min version
Downloads205K

Community Trust

Rating88/100
Number of ratings51
Active installs3K
Developer Profile

Basic Google Maps Placemarks Developer Profile

Ian Dunn

9 plugins · 5K total installs

86
trust score
Avg Security Score
88/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Basic Google Maps Placemarks

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/basic-google-maps-placemarks/css/style.css/wp-content/plugins/basic-google-maps-placemarks/css/marker.css/wp-content/plugins/basic-google-maps-placemarks/js/bgmp.js/wp-content/plugins/basic-google-maps-placemarks/js/bgmp-admin.js/wp-content/plugins/basic-google-maps-placemarks/js/bgmp-map.js/wp-content/plugins/basic-google-maps-placemarks/js/bgmp-list.js
Script Paths
/wp-content/plugins/basic-google-maps-placemarks/js/bgmp.js/wp-content/plugins/basic-google-maps-placemarks/js/bgmp-admin.js/wp-content/plugins/basic-google-maps-placemarks/js/bgmp-map.js/wp-content/plugins/basic-google-maps-placemarks/js/bgmp-list.js
Version Parameters
basic-google-maps-placemarks/css/style.css?ver=basic-google-maps-placemarks/css/marker.css?ver=basic-google-maps-placemarks/js/bgmp.js?ver=basic-google-maps-placemarks/js/bgmp-admin.js?ver=basic-google-maps-placemarks/js/bgmp-map.js?ver=basic-google-maps-placemarks/js/bgmp-list.js?ver=

HTML / DOM Fingerprints

CSS Classes
bgmp_mapbgmp_listbgmp-marker-icon-upload-previewbgmp-map-settings-wrapperbgmp-map-optionsbgmp-placemark-edit-form
HTML Comments
<!-- The following snippet of code must be placed in the head of your HTML document --><!-- The following snippet of code must be placed in the body of your HTML document --><!-- Shortcode: [bgmp-map] --><!-- Shortcode: [bgmp-list] -->
Data Attributes
data-bgmp-marker-iddata-bgmp-map-iddata-bgmp-map-options
JS Globals
bgmp_settingsbgmp_map_optionsbgmp_placemark_options
Shortcode Output
[bgmp-map][bgmp-list]
FAQ

Frequently Asked Questions about Basic Google Maps Placemarks