Google+ Comments Security & Risk Analysis

wordpress.org/plugins/google-plus-comments

The Google+ Comments WordPress plugin makes it easier for you to setup, administer and customise Google+ comments from your WordPress site.

40 active installs v1.0 PHP + WP 2.7+ Updated Apr 25, 2013
commentingcommentsgooglegoogle-plus
63
C · Use Caution
CVEs total1
Unpatched1
Last CVESep 26, 2025
Safety Verdict

Is Google+ Comments Safe to Use in 2026?

Use With Caution

Score 63/100

Google+ Comments has 1 unpatched vulnerability. Evaluate alternatives or apply available mitigations.

1 known CVE 1 unpatched Last CVE: Sep 26, 2025Updated 12yr ago
Risk Assessment

The `google-plus-comments` plugin v1.0 exhibits a mixed security posture. While it demonstrates good practices such as avoiding dangerous functions, using prepared statements for all SQL queries, and having no direct file operations or external HTTP requests, significant concerns remain. The plugin has a known vulnerability history with one unpatched medium severity CVE related to Cross-Site Scripting (XSS), which is a significant risk. The static analysis shows a low output escaping rate (17%), indicating a potential for XSS vulnerabilities in the 83% of outputs that are not properly escaped. Furthermore, the absence of nonce checks and capability checks on its single shortcode entry point is concerning, as this could allow for unauthorized actions or content injection if the shortcode's functionality is not inherently safe. The lack of taint analysis results is not necessarily positive, as it could indicate the analysis tool was unable to perform a thorough examination or that the plugin's code structure made it difficult to analyze for such vulnerabilities.

Key Concerns

  • Unpatched CVE exists
  • Low rate of proper output escaping
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
1

Google+ Comments Security Vulnerabilities

CVEs by Year

1 CVE in 2025 · unpatched
2025
Patched Has unpatched

Severity Breakdown

Medium
1

1 total CVE

CVE-2025-60186medium · 4.4Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Google+ Comments <= 1.0 - Authenticated (Administrator+) Stored Cross-Site Scripting

Sep 26, 2025Unpatched
Code Analysis
Analyzed Mar 16, 2026

Google+ Comments Code Analysis

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

Output Escaping

17% escaped12 total outputs
Attack Surface

Google+ Comments Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[gp-comments] class-frontend.php:93
WordPress Hooks 6
actionadmin_initclass-admin.php:9
actionadmin_menuclass-admin.php:27
actionwp_headclass-frontend.php:13
actionwp_headclass-frontend.php:24
filterthe_contentclass-frontend.php:57
filterwidget_textclass-frontend.php:92
Maintenance & Trust

Google+ Comments Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedApr 25, 2013
PHP min version
Downloads12K

Community Trust

Rating72/100
Number of ratings10
Active installs40
Developer Profile

Google+ Comments Developer Profile

Alex Moss

11 plugins · 4K total installs

67
trust score
Avg Security Score
83/100
Avg Patch Time
249 days
View full developer profile
Detection Fingerprints

How We Detect Google+ Comments

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

Asset Fingerprints

Script Paths
https://apis.google.com/js/plusone.js

HTML / DOM Fingerprints

HTML Comments
<!-- Google+ Comments for WordPress: http://3doordigital.com/wordpress/plugins/google-plus-comments/ -->
Data Attributes
data-hrefdata-num-postsdata-widthdata-colorscheme
Shortcode Output
<g:comments href="width="first_party_property="BLOGGER"view_type="FILTERED_POSTMOD"
FAQ

Frequently Asked Questions about Google+ Comments