Comment Autogrow Security & Risk Analysis

wordpress.org/plugins/comment-autogrow

Makes the comment textarea expand in height automatically

10 active installs v1.1.2 PHP + WP 2.8+ Updated Sep 13, 2012
autogrowcommentsjavascript
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Comment Autogrow Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The "comment-autogrow" plugin, version 1.1.2, exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code analysis reveals excellent security practices, with no dangerous functions, all SQL queries using prepared statements, and all outputs properly escaped. The lack of file operations, external HTTP requests, nonce checks, and capability checks (within the analyzed entry points) also contribute to its secure design. The taint analysis shows no identified flows with unsanitized paths, indicating a clean codebase regarding data manipulation vulnerabilities.

The vulnerability history is completely clean, with no recorded CVEs. This suggests a history of responsible development and maintenance. However, it is important to note that the static analysis reported 0 nonce checks and 0 capability checks. While the attack surface is currently zero, if any new entry points were to be introduced in future versions without proper authentication and authorization mechanisms, this could present a significant risk. Overall, the plugin appears to be very secure in its current state and version. The lack of any detected vulnerabilities or attack vectors is highly positive. The only area for potential improvement would be to ensure that any future expansion of its functionality includes robust security checks.

Vulnerabilities
None known

Comment Autogrow Security Vulnerabilities

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

Comment Autogrow Release Timeline

No version history available.
Code Analysis
Analyzed Mar 17, 2026

Comment Autogrow Code Analysis

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

Comment Autogrow Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actiontemplate_redirectcomment-autogrow.php:18
actionwp_footercomment-autogrow.php:19
Maintenance & Trust

Comment Autogrow Maintenance & Trust

Maintenance Signals

WordPress version tested3.0.5
Last updatedSep 13, 2012
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Comment Autogrow Developer Profile

scribu

24 plugins · 28K total installs

69
trust score
Avg Security Score
86/100
Avg Patch Time
4851 days
View full developer profile
Detection Fingerprints

How We Detect Comment Autogrow

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/comment-autogrow/growfield.js
Script Paths
/wp-content/plugins/comment-autogrow/growfield.js
Version Parameters
comment-autogrow/growfield.js?ver=

HTML / DOM Fingerprints

JS Globals
jQuery(document).ready(function($){ $('#comment').growfield(); });
FAQ

Frequently Asked Questions about Comment Autogrow