LogMyTrip Security & Risk Analysis

wordpress.org/plugins/logmytrip

Viewing your posts as a route plotted on a Google map is simple with this plugin. Just add the shortcode [logmytripmap] to a page to see the map.

40 active installs v1.9 PHP + WP 3.1+ Updated Feb 14, 2015
adventure-travelgoogle-mapmapsroute-mapstravel
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is LogMyTrip Safe to Use in 2026?

Generally Safe

Score 85/100

LogMyTrip has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The 'logmytrip' v1.9 plugin exhibits a generally good security posture with several positive indicators. The absence of known CVEs and the complete use of prepared statements for all SQL queries are significant strengths. Furthermore, the presence of nonce and capability checks for its entry points, along with proper escaping for a majority of its output, suggests a developer who is aware of common security best practices. However, there are areas for improvement. The taint analysis reveals flows with unsanitized paths, which, despite not being classified as critical or high severity in this instance, represent a potential risk if not carefully monitored or if the plugin is updated without addressing these. Additionally, the 37% of output that is not properly escaped could lead to cross-site scripting (XSS) vulnerabilities, depending on the context of the data being outputted and whether it's user-controlled.

Key Concerns

  • Unsanitized paths in taint flows
  • Significant percentage of unescaped output
Vulnerabilities
None known

LogMyTrip Security Vulnerabilities

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

LogMyTrip Code Analysis

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

SQL Query Safety

100% prepared2 total queries

Output Escaping

63% escaped24 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
logtripmap (logmytrip.php:137)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

LogMyTrip Attack Surface

Entry Points2
Unprotected0

Shortcodes 2

[logmytrip] logmytrip.php:31
[logmytripmap] logmytrip.php:32
WordPress Hooks 8
actionwp_headlogmytrip.php:33
actionwp_footerlogmytrip.php:34
filterthe_contentlogmytrip.php:35
actionadmin_head-post-new.phplogmytrip.php:36
actionadmin_head-post.phplogmytrip.php:37
actionadmin_menulogmytrip.php:38
actionsave_postlogmytrip.php:39
actiondbx_post_advancedlogmytrip.php:250
Maintenance & Trust

LogMyTrip Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedFeb 14, 2015
PHP min version
Downloads7K

Community Trust

Rating0/100
Number of ratings0
Active installs40
Developer Profile

LogMyTrip Developer Profile

ajohnwaters

1 plugin · 40 total installs

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

How We Detect LogMyTrip

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

Asset Fingerprints

Script Paths
/wp-content/plugins/logmytrip/logmytrip.php

HTML / DOM Fingerprints

JS Globals
Addressplacedatepccaptionhtml+10 more
Shortcode Output
<div id="maptitle"></div><div id="mainmap"></div>
FAQ

Frequently Asked Questions about LogMyTrip