Tracking Code for Google Tag Manager Security & Risk Analysis

wordpress.org/plugins/tracking-code-for-google-tag-manager

Simple, lightweight solution for inserting your Google Tag Manager Universal tracking code.

20 active installs v1.0.0 PHP 5.6+ WP 5.2+ Updated Jul 5, 2024
containergooglegoogle-tag-managertag-managertracking-code
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Tracking Code for Google Tag Manager Safe to Use in 2026?

Generally Safe

Score 92/100

Tracking Code for Google Tag Manager has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The plugin "tracking-code-for-google-tag-manager" version 1.0.0 demonstrates a strong security posture based on the provided static analysis. The absence of any identified dangerous functions, raw SQL queries, or unescaped output indicates good development practices. The plugin also has a clean vulnerability history, with no known CVEs recorded. The lack of an attack surface, such as AJAX handlers, REST API routes, or shortcodes, further contributes to its secure design by minimizing potential entry points for attackers. The absence of taint flows with unsanitized paths is also a positive indicator. While the current analysis shows no immediate risks, it's important to note the complete lack of nonce and capability checks. While not an immediate vulnerability in this specific analysis due to the zero attack surface, this is a significant weakness that could become exploitable if functionality were added or modified without incorporating proper authorization checks. The overall assessment is positive, but the lack of inherent authorization mechanisms warrants attention for future development.

Key Concerns

  • No nonce checks implemented
  • No capability checks implemented
Vulnerabilities
None known

Tracking Code for Google Tag Manager Security Vulnerabilities

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

Tracking Code for Google Tag Manager Release Timeline

v1.0.0Current
Code Analysis
Analyzed Mar 16, 2026

Tracking Code for Google Tag Manager Code Analysis

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

Output Escaping

100% escaped6 total outputs
Attack Surface

Tracking Code for Google Tag Manager Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_initinc\admin.php:13
actionwp_headinc\public.php:13
actionwp_body_openinc\public.php:50
Maintenance & Trust

Tracking Code for Google Tag Manager Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.0
Last updatedJul 5, 2024
PHP min version5.6
Downloads1K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

Tracking Code for Google Tag Manager Developer Profile

Clayton Collie

5 plugins · 170 total installs

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

How We Detect Tracking Code for Google Tag Manager

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

Asset Fingerprints

Script Paths
https://www.googletagmanager.com/gtm.js

HTML / DOM Fingerprints

HTML Comments
<!-- Google Tag Manager --><!-- End Google Tag Manager --><!-- Google Tag Manager (noscript) --><!-- End Google Tag Manager (noscript) -->
JS Globals
dataLayer
FAQ

Frequently Asked Questions about Tracking Code for Google Tag Manager