Simple Google Contact Map Security & Risk Analysis

wordpress.org/plugins/simple-google-contact-map

Simple embedded Google Map to any Post or Page Using shortcode and Widget.

30 active installs v1.0 PHP + WP 3.3+ Updated Sep 8, 2015
contactcontact-mapdirectiongoogle-mapmaps
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Simple Google Contact Map Safe to Use in 2026?

Generally Safe

Score 85/100

Simple Google Contact Map has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The "simple-google-contact-map" v1.0 plugin exhibits a mixed security posture. On the positive side, it has a very small attack surface with only one shortcode and no AJAX handlers or REST API routes, which are common vectors for exploits. Furthermore, all SQL queries are properly prepared, and there are no recorded vulnerabilities (CVEs), suggesting a history of responsible development or a lack of previous targeted attacks. However, significant concerns arise from the static analysis. The presence of dangerous functions like `unserialize` and `create_function` is a major red flag, as these can be exploited for remote code execution if user-supplied data is passed to them without proper sanitization. The low percentage of properly escaped output (29%) is also worrying, increasing the risk of cross-site scripting (XSS) vulnerabilities. The absence of nonce checks, while not directly exploitable given the limited attack surface, is a missed opportunity for defense-in-depth.

Key Concerns

  • Dangerous functions (unserialize, create_function)
  • Low percentage of output escaping
  • No nonce checks
Vulnerabilities
None known

Simple Google Contact Map Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Simple Google Contact Map Release Timeline

v1.0Current
Code Analysis
Analyzed Apr 16, 2026

Simple Google Contact Map Code Analysis

Dangerous Functions
3
Raw SQL Queries
0
0 prepared
Unescaped Output
25
10 escaped
Nonce Checks
0
Capability Checks
1
File Operations
0
External Requests
1
Bundled Libraries
0

Dangerous Functions Found

unserialize$map_info = unserialize(get_option('sgcm_options'));googlemap-sgcm.php:44
create_functionadd_action( 'widgets_init', create_function('', 'return register_widget("Sgcm_Widget");'));googlemap-sgcm.php:178
unserialize$map_info = unserialize(get_option('sgcm_options'));options.php:112

Output Escaping

29% escaped35 total outputs
Attack Surface

Simple Google Contact Map Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[sgcm_map] googlemap-sgcm.php:75
WordPress Hooks 3
actionadmin_menugooglemap-sgcm.php:39
actionadmin_initgooglemap-sgcm.php:82
actionwidgets_initgooglemap-sgcm.php:178
Maintenance & Trust

Simple Google Contact Map Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedSep 8, 2015
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

Simple Google Contact Map Developer Profile

praveencrony

4 plugins · 3K total installs

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

How We Detect Simple Google Contact Map

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/simple-google-contact-map/css/sgcm-map.css

HTML / DOM Fingerprints

CSS Classes
Sgcm_Widget
Data Attributes
id="sgc-map-option"
Shortcode Output
<iframe width= height= frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="https://maps.google.com/maps??hl=&amp;ie=utf8&amp;output=embed&amp;iwd=1&amp;mrt=loc&amp;t=
FAQ

Frequently Asked Questions about Simple Google Contact Map