IntenseDebate Comments Security & Risk Analysis

wordpress.org/plugins/intensedebate

IntenseDebate comments enhance and encourage conversation on your blog. Build your reader community, increase your comments, & boost pageviews.

500 active installs v2.10.2 PHP + WP 5.0+ Updated Feb 21, 2023
avatarscommunityprofilespamwidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is IntenseDebate Comments Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 3yr ago
Risk Assessment

The IntenseDebate plugin version 2.10.2 exhibits a generally strong security posture with no recorded past vulnerabilities or critical findings in static analysis. The absence of known CVEs and critical taint flows is a positive indicator of its security development practices. The plugin also shows good adherence to modern WordPress security by primarily utilizing prepared statements for SQL queries and including a reasonable number of nonce and capability checks. However, a significant concern arises from the output escaping, where only 23% of outputs are properly escaped. This suggests a potential for Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is not handled securely before being rendered in the browser. While the attack surface appears minimal with no identified unprotected entry points, the low rate of proper output escaping presents a notable risk that requires attention and remediation.

Key Concerns

  • Low percentage of properly escaped output
Vulnerabilities
None known

IntenseDebate Comments Security Vulnerabilities

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

IntenseDebate Comments Code Analysis

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

SQL Query Safety

88% prepared17 total queries

Output Escaping

23% escaped35 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

7 flows3 with unsanitized paths
id_SETTINGS_skip_import (intensedebate.php:2288)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

IntenseDebate Comments Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 41
actionadmin_headintensedebate.php:90
actioninitintensedebate.php:95
actionadmin_noticesintensedebate.php:98
actionadmin_menuintensedebate.php:101
actioninitintensedebate.php:102
actionadmin_headintensedebate.php:106
filterallowed_optionsintensedebate.php:109
actionadmin_print_footer_scriptsintensedebate.php:113
actionadmin_print_footer_scriptsintensedebate.php:119
actionwp_insert_commentintensedebate.php:124
actiontrackback_postintensedebate.php:125
actionpingback_postintensedebate.php:126
actionedit_commentintensedebate.php:127
actionsave_postintensedebate.php:128
actiondelete_postintensedebate.php:129
actionwp_set_comment_statusintensedebate.php:130
actiontrashed_commentintensedebate.php:131
actionuntrashed_commentintensedebate.php:132
actionload-options.phpintensedebate.php:135
filtercomments_templateintensedebate.php:140
filtercomments_numberintensedebate.php:143
actionwp_footerintensedebate.php:144
actionget_footerintensedebate.php:145
filteroption_moderation_notifyintensedebate.php:150
filteroption_comments_notifyintensedebate.php:151
actionshutdownintensedebate.php:156
actionedit_commentintensedebate.php:653
actionwp_insert_commentintensedebate.php:654
actionedit_commentintensedebate.php:659
actionwp_insert_commentintensedebate.php:660
actionsave_postintensedebate.php:791
actionedit_postintensedebate.php:795
actionwp_set_comment_statusintensedebate.php:1280
actionwp_set_comment_statusintensedebate.php:1330
filtercomments_templateintensedebate.php:2474
actiontrashed_commentintensedebate.php:2549
actionwp_set_comment_statusintensedebate.php:2550
actionplugins_loadedintensedebate.php:2565
actionplugins_loadedintensedebate.php:2603
actionplugins_loadedintensedebate.php:2641
actionplugins_loadedintensedebate.php:2679
Maintenance & Trust

IntenseDebate Comments Maintenance & Trust

Maintenance Signals

WordPress version tested6.1.10
Last updatedFeb 21, 2023
PHP min version
Downloads590K

Community Trust

Rating44/100
Number of ratings9
Active installs500
Developer Profile

IntenseDebate Comments Developer Profile

Automattic

213 plugins · 19.2M total installs

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

How We Detect IntenseDebate Comments

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/intensedebate/comments.png/wp-content/plugins/intensedebate/admin-style.css/wp-content/plugins/intensedebate/admin-script.js
Script Paths
/wp-content/plugins/intensedebate/admin-script.js
Version Parameters
intensedebate/comments.png?ver=intensedebate/admin-style.css?ver=intensedebate/admin-script.js?ver=

HTML / DOM Fingerprints

CSS Classes
id_settings_page
HTML Comments
<!-- ID Plugin Deactivation --><!-- IntenseDebate Admin Notices --><!-- ID Comment moderation --><!-- ID Settings page -->+4 more
Data Attributes
data-id-actiondata-id-comment-iddata-id-post-iddata-id-targetdata-id-post-titledata-id-post-url+5 more
JS Globals
id_ajaxurlid_varsID_debug
FAQ

Frequently Asked Questions about IntenseDebate Comments