Google Tag Manager Security & Risk Analysis

wordpress.org/plugins/google-tag-manager

The Google Tag Manager plugin adds a field to the existing General Settings page for the ID and outputs the javascript to make it work.

10K active installs v1.0.3 PHP + WP 2.7+ Updated Apr 30, 2020
analyticsgoogletag-managementtag-managertheme-hook-alliance
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Google Tag Manager Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

The "google-tag-manager" plugin version 1.0.3 exhibits a strong security posture based on the provided static analysis. There are no identified entry points such as AJAX handlers, REST API routes, shortcodes, or cron events that are exposed without proper authentication checks. The code signals further reinforce this positive assessment, with no dangerous functions, no raw SQL queries (all using prepared statements), no file operations, and no external HTTP requests. The absence of taint analysis findings and a clean vulnerability history, with zero known CVEs, further suggests a robustly developed and maintained plugin. The plugin also demonstrates good output escaping practices, with 80% of outputs being properly escaped.

While the plugin performs well in the analyzed areas, the lack of nonce checks and capability checks on potential entry points is a slight concern, although the absence of any entry points mitigates this risk significantly in this version. The fact that there are no recorded vulnerabilities over its history is a testament to its secure development and the vigilance of its maintainers. Overall, this plugin appears to be a very safe option, with a minimal attack surface and a strong adherence to secure coding principles, making it a low-risk choice for WordPress users.

Key Concerns

  • No capability checks on entry points
  • No nonce checks on entry points
  • Output escaping not 100%
Vulnerabilities
None known

Google Tag Manager Security Vulnerabilities

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

Google Tag Manager Code Analysis

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

Output Escaping

80% escaped5 total outputs
Attack Surface

Google Tag Manager Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
filteradmin_initgoogle-tag-manager.php:17
actionwp_headgoogle-tag-manager.php:18
actionwp_body_opengoogle-tag-manager.php:19
actiongenesis_beforegoogle-tag-manager.php:20
actiontha_body_topgoogle-tag-manager.php:21
actionbody_topgoogle-tag-manager.php:22
actionwp_footergoogle-tag-manager.php:23
Maintenance & Trust

Google Tag Manager Maintenance & Trust

Maintenance Signals

WordPress version tested5.4.19
Last updatedApr 30, 2020
PHP min version
Downloads178K

Community Trust

Rating84/100
Number of ratings10
Active installs10K
Developer Profile

Google Tag Manager Developer Profile

George Stephanis

16 plugins · 16K total installs

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

How We Detect 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?id=https://www.googletagmanager.com/ns.html?id=

HTML / DOM Fingerprints

HTML Comments
<!-- Google Tag Manager --><!-- End Google Tag Manager --><!-- Google Tag Manager (noscript) --><!-- End Google Tag Manager (noscript) -->
Data Attributes
id="google_tag_manager_id"name="google_tag_manager_id"class="regular-text code"placeholder="ABC-DEFG"
JS Globals
dataLayer
FAQ

Frequently Asked Questions about Google Tag Manager