Comments Security & Risk Analysis

wordpress.org/plugins/advanced-comments

Customize and optimize comments in WordPress

100 active installs v1.0.0 PHP + WP 3.0+ Updated Dec 9, 2016
commentcomment-formcommentingcomments
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Comments Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 9yr ago
Risk Assessment

The "advanced-comments" plugin v1.0.0 exhibits a generally strong security posture in terms of its attack surface and known vulnerability history. The absence of any recorded CVEs, coupled with the static analysis showing zero entry points and no dangerous functions, suggests a cautious development approach. Furthermore, all SQL queries are correctly utilizing prepared statements, which is a significant strength.

However, a critical concern arises from the static analysis revealing that 100% of outputs are not properly escaped. This presents a significant risk of Cross-Site Scripting (XSS) vulnerabilities, as user-supplied data could be injected into the output without sanitization, potentially leading to malicious script execution. The lack of nonce checks and capability checks, while not directly exploitable due to the limited attack surface shown, is a missed opportunity for robust security practices.

The plugin's vulnerability history is clean, which is positive. This could indicate diligent development or simply a short history without significant security testing. The overall conclusion is that while the plugin avoids common pitfalls like direct SQL injection and has a clean CVE record, the widespread lack of output escaping is a serious oversight that needs immediate attention.

Key Concerns

  • 100% of outputs are not properly escaped
  • No nonce checks implemented
  • No capability checks implemented
Vulnerabilities
None known

Comments Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Comments Release Timeline

v1.0.0Current
Code Analysis
Analyzed Mar 16, 2026

Comments Code Analysis

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

Output Escaping

0% escaped6 total outputs
Attack Surface

Comments Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menuadmin\comments_admin.php:8
actionadmin_initadmin\comments_admin.php:9
filtercomments_openfrontend\comments_frontend.php:12
actionplugins_loadedinc\comments_main.php:21
Maintenance & Trust

Comments Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedDec 9, 2016
PHP min version
Downloads10K

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

Comments Developer Profile

Rock Solid

7 plugins · 16K total installs

73
trust score
Avg Security Score
91/100
Avg Patch Time
223 days
View full developer profile
Detection Fingerprints

How We Detect Comments

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/advanced-comments/admin/css/admin.css/wp-content/plugins/advanced-comments/admin/js/admin.js/wp-content/plugins/advanced-comments/frontend/css/frontend.css/wp-content/plugins/advanced-comments/frontend/js/frontend.js
Script Paths
/wp-content/plugins/advanced-comments/admin/js/admin.js/wp-content/plugins/advanced-comments/frontend/js/frontend.js
Version Parameters
advanced-comments/admin/css/admin.css?ver=advanced-comments/admin/js/admin.js?ver=advanced-comments/frontend/css/frontend.css?ver=advanced-comments/frontend/js/frontend.js?ver=

HTML / DOM Fingerprints

CSS Classes
comments-admin-wrapcomments-frontend-wrap
FAQ

Frequently Asked Questions about Comments