Caret Ez Google Maps Security & Risk Analysis

wordpress.org/plugins/caret-ez-google-maps

Google Maps 簡単挿入プラグイン - Caret Ez Google Maps

10 active installs v1.0.1 PHP + WP 3.0.0+ Updated Aug 6, 2018
careteasyezgooglemaps
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Caret Ez Google Maps Safe to Use in 2026?

Generally Safe

Score 85/100

Caret Ez Google Maps 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 security analysis of caret-ez-google-maps v1.0.1 reveals a plugin with a seemingly limited attack surface, as indicated by zero identified entry points such as AJAX handlers, REST API routes, shortcodes, or cron events. The code also demonstrates good practices in relation to SQL queries, exclusively using prepared statements, and shows no file operations or external HTTP requests. Furthermore, the absence of known vulnerabilities in its history suggests a generally stable and well-maintained component.

However, a significant concern arises from the output escaping analysis. With one total output and zero percent properly escaped, this indicates a high potential for Cross-Site Scripting (XSS) vulnerabilities. Any data displayed to users that is not properly escaped can be manipulated by attackers to inject malicious scripts. The lack of nonce checks also contributes to a potential security weakness, although this is mitigated by the absence of AJAX and REST API entry points which would typically leverage nonces for protection.

Despite the strong indications of secure coding practices in areas like SQL and the lack of a vulnerability history, the unescaped output represents a critical blind spot. Until this is addressed, the plugin carries a notable risk of XSS attacks, which could compromise user sessions or inject malicious content into the WordPress site.

Key Concerns

  • Output is not properly escaped
Vulnerabilities
None known

Caret Ez Google Maps Security Vulnerabilities

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

Caret Ez Google Maps Release Timeline

v1.0.1Current
v1.0.0
Code Analysis
Analyzed Mar 17, 2026

Caret Ez Google Maps Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Caret Ez Google Maps Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
actionplugins_loadedCaretEzGoogleMaps.php:31
filtermce_pluginsCaretEzGoogleMaps.php:36
actioninitCaretEzGoogleMaps.php:41
filtermce_external_pluginsCaretEzGoogleMaps.php:49
filtermce_buttonsCaretEzGoogleMaps.php:50
filterthe_contentCaretEzGoogleMaps.php:114
actioninitCaretEzGoogleMaps.php:115
actionadmin_print_footer_scriptsCaretEzGoogleMaps.php:116
actionwp_footerCaretEzGoogleMaps.php:117
Maintenance & Trust

Caret Ez Google Maps Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedAug 6, 2018
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Caret Ez Google Maps Developer Profile

garantieticaret

4 plugins · 220 total installs

74
trust score
Avg Security Score
93/100
Avg Patch Time
166 days
View full developer profile
Detection Fingerprints

How We Detect Caret Ez Google Maps

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/CaretEzGoogleMaps/style.css/wp-content/plugins/CaretEzGoogleMaps/CaretEzGoogleMaps.ui.js
Script Paths
/wp-content/plugins/CaretEzGoogleMaps/CaretEzGoogleMaps.js
Version Parameters
CaretEzGoogleMaps/style.css?ver=CaretEzGoogleMaps/CaretEzGoogleMaps.ui.js?ver=

HTML / DOM Fingerprints

CSS Classes
CaretEzGoogleMaps
JS Globals
googlemap_init
Shortcode Output
[GoogleMaps]{GoogleMaps}{/GoogleMaps}
FAQ

Frequently Asked Questions about Caret Ez Google Maps