Google Plusone(+1) Button Security & Risk Analysis

wordpress.org/plugins/googleplusone-button

Author Site|

10 active installs v1.2 PHP + WP 3.0+ Updated Jul 8, 2011
google-1google-1-buttongoogle-plus-onegoogle-plus-one-buttongoogle-plusone1-button
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Google Plusone(+1) Button Safe to Use in 2026?

Generally Safe

Score 85/100

Google Plusone(+1) Button has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 14yr ago
Risk Assessment

The "googleplusone-button" v1.2 plugin exhibits a generally positive security posture in several key areas. It demonstrates an absence of known vulnerabilities (CVEs), no recorded critical or high-severity issues, and no direct SQL queries that are not prepared. The plugin also avoids file operations and external HTTP requests, further reducing its attack surface. However, a significant concern arises from the static analysis revealing that 100% of its 19 output points are not properly escaped. This lack of output sanitization presents a substantial risk of Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected and executed within the user's browser.

Key Concerns

  • 100% of output is not properly escaped
  • No nonce checks on any entry points
  • Only one capability check found
Vulnerabilities
None known

Google Plusone(+1) Button Security Vulnerabilities

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

Google Plusone(+1) Button Code Analysis

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

Output Escaping

0% escaped19 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
gpo_admin_page (googleplusone-button-admin.php:60)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Google Plusone(+1) Button Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[twg_gpo_button] googleplusone-button-shortcode.php:10
WordPress Hooks 6
actionwp_print_scriptsgoogleplusone-button-display.php:9
actionadmin_menugoogleplusone-button.php:33
actionadmin_initgoogleplusone-button.php:34
actioninitgoogleplusone-button.php:38
filterthe_contentgoogleplusone-button.php:39
filterthe_excerptgoogleplusone-button.php:40
Maintenance & Trust

Google Plusone(+1) Button Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedJul 8, 2011
PHP min version
Downloads7K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Google Plusone(+1) Button Developer Profile

webgig

1 plugin · 10 total installs

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

How We Detect Google Plusone(+1) Button

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/googleplusone-button/css/googleplusone-button.css/wp-content/plugins/googleplusone-button/js/googleplusone-button.js
Script Paths
https://apis.google.com/js/plusone.js

HTML / DOM Fingerprints

CSS Classes
wrapupdatedmessageelement
Data Attributes
twg_gpo_button_sizetwg_gpo_include_counttwg_gpo_button_locationtwg_gpo_button_languagetwg_gpo_button_display_in
FAQ

Frequently Asked Questions about Google Plusone(+1) Button