Pixel & tracking codes for Google Web stories (formerly AMP Stories) Security & Risk Analysis

wordpress.org/plugins/pixel-for-web-stories

Pixel for Web Stories (Google) allows you to (re)add easily your tracking codes |Pixel (Facebook, Linkedin, Pinterest, Tiktok, Twitter, Yandex, Snapc …

30 active installs v1.0.6 PHP 5.6+ WP 4.1+ Updated Jan 18, 2026
ampgooglepixelretargetingstories
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Pixel & tracking codes for Google Web stories (formerly AMP Stories) Safe to Use in 2026?

Generally Safe

Score 100/100

Pixel & tracking codes for Google Web stories (formerly AMP Stories) has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2mo ago
Risk Assessment

The plugin "pixel-for-web-stories" v1.0.6 exhibits a generally good security posture based on the provided static analysis. The absence of any known CVEs in its history is a significant strength, indicating a history of responsible development and maintenance. Furthermore, the analysis shows no critical or high-severity issues in taint flows, no direct SQL queries without prepared statements, and a reasonable number of nonce and capability checks, suggesting an awareness of common WordPress security pitfalls. The limited attack surface, with zero AJAX handlers, REST API routes, shortcodes, and cron events, further contributes to a lower potential for external exploitation.

Key Concerns

  • Moderate percentage of unescaped output
  • Bundled Freemius library at v1.0
Vulnerabilities
None known

Pixel & tracking codes for Google Web stories (formerly AMP Stories) Security Vulnerabilities

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

Pixel & tracking codes for Google Web stories (formerly AMP Stories) Code Analysis

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

Bundled Libraries

Freemius1.0

Output Escaping

52% escaped58 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
page (admin\controllers\SettingsController.php:9)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Pixel & tracking codes for Google Web stories (formerly AMP Stories) Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
actionweb_stories_print_analyticsadmin\controllers\TrackingController.php:8
actionadmin_menuadmin\Settings.php:10
actionadmin_enqueue_scriptsadmin\Settings.php:15
filterconnect_urlpixel-for-web-stories.php:74
filterafter_skip_urlpixel-for-web-stories.php:75
filterafter_connect_urlpixel-for-web-stories.php:76
filterafter_pending_connect_urlpixel-for-web-stories.php:77
filterconnect_messagepixel-for-web-stories.php:93
actioninitpixel-for-web-stories.php:102
Maintenance & Trust

Pixel & tracking codes for Google Web stories (formerly AMP Stories) Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedJan 18, 2026
PHP min version5.6
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

Pixel & tracking codes for Google Web stories (formerly AMP Stories) Developer Profile

Pagup

17 plugins · 33K total installs

78
trust score
Avg Security Score
98/100
Avg Patch Time
439 days
View full developer profile
Detection Fingerprints

How We Detect Pixel & tracking codes for Google Web stories (formerly AMP Stories)

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/pixel-for-web-stories/admin/assets/js/pixel-for-web-stories.js
Script Paths
/wp-content/plugins/pixel-for-web-stories/vendor/freemius/start.php

HTML / DOM Fingerprints

CSS Classes
pfws-logopfws-tabpfws-containerpfws-segment
Data Attributes
page=pixel-for-web-stories
FAQ

Frequently Asked Questions about Pixel & tracking codes for Google Web stories (formerly AMP Stories)