Inspectlet Websites HeadMap Security & Risk Analysis

wordpress.org/plugins/inspectlet-websites-headmap

This plugins allows us to add the script code from Inspectlet Free Plan

10 active installs v1.0.3 PHP + WP 2.8+ Updated Feb 13, 2014
featured-imagerss
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Inspectlet Websites HeadMap Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 12yr ago
Risk Assessment

The 'inspectlet-websites-headmap' plugin exhibits a generally good security posture based on the static analysis. There are no detected dangerous functions, SQL queries utilize prepared statements exclusively, and there are no file operations or external HTTP requests, all of which are positive indicators. However, a significant concern arises from the output escaping analysis, where 100% of outputs are not properly escaped. This indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities, allowing attackers to inject malicious scripts into the website's content.

The taint analysis reveals two flows with unsanitized paths. While these are not classified as critical or high severity, they still represent potential pathways for data to be processed without adequate sanitization, which could be exploited in conjunction with other weaknesses. The plugin's vulnerability history is clean, with no recorded CVEs, suggesting a lack of known publicly disclosed vulnerabilities. This, combined with the absence of an attack surface, is a positive sign, but it does not mitigate the risks identified in the code analysis.

In conclusion, the plugin has strengths in its lack of an attack surface and secure handling of SQL and external requests. Nevertheless, the complete lack of output escaping is a critical flaw that exposes users to XSS attacks. The unsanitized taint flows also warrant attention. A balanced view shows a plugin that avoids common pitfalls but has a severe, unaddressed weakness in output sanitization.

Key Concerns

  • 100% of outputs unescaped
  • Taint flows with unsanitized paths
Vulnerabilities
None known

Inspectlet Websites HeadMap Security Vulnerabilities

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

Inspectlet Websites HeadMap Code Analysis

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

Output Escaping

0% escaped3 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
options_page (inspectlet.php:72)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Inspectlet Websites HeadMap Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menuinspectlet.php:21
filterplugin_action_linksinspectlet.php:22
actionwp_headinspectlet.php:27
Maintenance & Trust

Inspectlet Websites HeadMap Maintenance & Trust

Maintenance Signals

WordPress version tested3.7.41
Last updatedFeb 13, 2014
PHP min version
Downloads2K

Community Trust

Rating20/100
Number of ratings1
Active installs10
Developer Profile

Inspectlet Websites HeadMap Developer Profile

David Garcia

11 plugins · 90 total installs

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

How We Detect Inspectlet Websites HeadMap

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

Asset Fingerprints

Script Paths
/wp-content/plugins/inspectlet-websites-headmap/inspectlet.php

HTML / DOM Fingerprints

HTML Comments
<!-- Begin Inspectlet Embed Code --><!-- End Inspectlet Embed Code -->
JS Globals
window.__insp__insp
FAQ

Frequently Asked Questions about Inspectlet Websites HeadMap