Comments Disclaimer Security & Risk Analysis

wordpress.org/plugins/comments-disclaimer

A minimalist and essential plugin that will add a public comments disclaimer to your site. Protect yourself from liabilities for user-generated commen …

0 active installs v1.0 PHP 7.3+ WP 5.8+ Updated Apr 15, 2025
commentscomments-disclaimerdisclaimer
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Comments Disclaimer Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The "comments-disclaimer" plugin v1.0 exhibits a strong security posture based on the provided static analysis. It has a remarkably small attack surface with no detectable AJAX handlers, REST API routes, shortcodes, or cron events. The code also demonstrates good practices by not utilizing dangerous functions, performing file operations, or making external HTTP requests. All SQL queries are 100% prepared, and a nonce check and capability check are present, which are positive signs for input validation and access control.

However, a notable concern arises from the output escaping. With 10 total outputs analyzed, only 20% are properly escaped. This significantly increases the risk of cross-site scripting (XSS) vulnerabilities, especially if the plugin handles user-supplied data or dynamic content that is then displayed on the front end. The absence of any recorded vulnerabilities in its history is positive, suggesting a well-maintained codebase so far, but it does not negate the potential risks identified in the static analysis. Overall, while the plugin has a minimal attack surface and good practices in many areas, the poor output escaping is a critical weakness that needs to be addressed to mitigate XSS risks.

Key Concerns

  • Poor output escaping
Vulnerabilities
None known

Comments Disclaimer Security Vulnerabilities

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

Comments Disclaimer Release Timeline

v1.0Current
Code Analysis
Analyzed Mar 17, 2026

Comments Disclaimer Code Analysis

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

Output Escaping

20% escaped10 total outputs
Attack Surface

Comments Disclaimer Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
actionadmin_menucomments-disclaimer.php:20
actionsave_postcomments-disclaimer.php:21
actioncomment_form_beforecomments-disclaimer.php:22
actionwp_enqueue_scriptscomments-disclaimer.php:24
actionadmin_menucomments-disclaimer.php:25
filterplugin_action_linkscomments-disclaimer.php:26
actionadmin_initcomments-disclaimer.php:27
actionadmin_post_add_comments_disclaimer_to_existing_postscomments-disclaimer.php:28
actionplugins_loadedcomments-disclaimer.php:29
Maintenance & Trust

Comments Disclaimer Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedApr 15, 2025
PHP min version7.3
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Comments Disclaimer Developer Profile

Alan Jacob Mathew

4 plugins · 20 total installs

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

How We Detect Comments Disclaimer

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

Asset Fingerprints

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

HTML / DOM Fingerprints

CSS Classes
comments-messagemessage-content
Data Attributes
id="comment_disclaimer_checkbox"name="comment_disclaimer_checkbox"
Shortcode Output
<p class="message-content">Disclaimer: The comments sect
FAQ

Frequently Asked Questions about Comments Disclaimer