
Google SEO Pressor for Rich snippets Security & Risk Analysis
wordpress.org/plugins/google-seo-author-snippetsEnrich your WordPress website content with Google Structured Data and make it more SEO friendly.
Is Google SEO Pressor for Rich snippets Safe to Use in 2026?
High Risk
Score 42/100Google SEO Pressor for Rich snippets carries significant security risk with 3 known CVEs, 2 still unpatched. Consider switching to a maintained alternative.
The google-seo-author-snippets plugin exhibits a mixed security posture. On the positive side, the code demonstrates strong practices in SQL query preparation and output escaping, with very few instances of raw SQL or unescaped output. The absence of file operations and external HTTP requests further reduces potential attack vectors.
However, significant concerns arise from the static analysis. A substantial attack surface is exposed through 7 AJAX handlers, all of which lack authentication checks. While taint analysis shows no critical or high-severity vulnerabilities, the presence of 2 flows with unsanitized paths is concerning. The plugin's vulnerability history is particularly alarming, with 3 known medium-severity CVEs, 2 of which remain unpatched. These historical vulnerabilities include Cross-Site Request Forgery, Missing Authorization, and Cross-site Scripting, indicating recurring security weaknesses.
In conclusion, while the plugin shows strengths in core coding practices like query sanitization and output escaping, the lack of authentication on a majority of its entry points and its history of unpatched vulnerabilities present a considerable risk. The unpatched CVEs, especially given their types, are a major red flag. Users should exercise extreme caution.
Key Concerns
- 7 unprotected AJAX handlers
- 2 unpatched medium CVEs
- 2 flows with unsanitized paths
- Only 1 nonce check for 7 entry points
- 0 capability checks on entry points
Google SEO Pressor for Rich snippets Security Vulnerabilities
CVEs by Year
Severity Breakdown
3 total CVEs
Google SEO Pressor Snippet <= 2.0 - Cross-Site Request Forgery
Google SEO Pressor Snippet <= 2.0 - Missing Authorization
Google SEO Pressor for Rich snippets <= 1.2.2 - Cross-Site Scripting
Google SEO Pressor for Rich snippets Code Analysis
SQL Query Safety
Output Escaping
Data Flow Analysis
Google SEO Pressor for Rich snippets Attack Surface
AJAX Handlers 7
WordPress Hooks 29
Maintenance & Trust
Google SEO Pressor for Rich snippets Maintenance & Trust
Maintenance Signals
Community Trust
Google SEO Pressor for Rich snippets Alternatives
Simply Sociable
simply-sociable
Adds social media links for Google+, Twitter, and Facebook to the bottom of each blog post.
Insert Headers And Footers
wp-headers-and-footers
Include inline javascript, stylesheets, CSS code or anything you want in Header and Footer areas of your WordPress with ease.
Nextend Social Login and Register
nextend-facebook-connect
One click registration & login plugin for Facebook, Google, X (formerly Twitter) and more. Quick setup and easy configuration.
VK All in One Expansion Unit
vk-all-in-one-expansion-unit
This plug-in is an integrated plug-in with a variety of features that make it powerful your web site.
Product Feed PRO for WooCommerce by AdTribes – Product Feeds for WooCommerce
woo-product-feed-pro
Most popular WooCommerce product feed plugin supporting Google shopping feed, meta/facebook feed, bing product feed & more.
Google SEO Pressor for Rich snippets Developer Profile
20 plugins · 40K total installs
How We Detect Google SEO Pressor for Rich snippets
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/google-seo-author-snippets/js/smack-microdata.js/wp-content/plugins/google-seo-author-snippets/js/google_seo_meta_box.css/wp-content/plugins/google-seo-author-snippets/css/style.cssjs/smack-microdata.jsjs/google_seo_meta_box.csscss/style.cssgoogle-seo-author-snippets/js/smack-microdata.js?ver=google-seo-author-snippets/js/google_seo_meta_box.css?ver=google-seo-author-snippets/css/style.css?ver=