@reply Security & Risk Analysis

wordpress.org/plugins/at-reply

Automagically link Twitterish "@name:" replies in comments.

10 active installs v1.1 PHP + WP 2.1+ Updated Mar 5, 2008
commentsfilterreplytwitterwpmu
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is @reply Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 18yr ago
Risk Assessment

The "at-reply" plugin v1.1 exhibits an exceptionally strong security posture based on the provided static analysis. The absence of any detectable AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code analysis reveals a clean bill of health regarding dangerous functions, raw SQL queries, unescaped output, file operations, external HTTP requests, and insufficient nonce or capability checks. The taint analysis also shows no identified security flows, indicating that user-supplied data is not being improperly handled. The plugin's vulnerability history is completely clear, with no recorded CVEs, which suggests a history of secure development and maintenance. This combination of a minimal attack surface, clean code practices, and a spotless vulnerability record points to a highly secure plugin.

Vulnerabilities
None known

@reply Security Vulnerabilities

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

@reply 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

@reply Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
filtercomment_textat-reply.php:37
Maintenance & Trust

@reply Maintenance & Trust

Maintenance Signals

WordPress version tested2.5
Last updatedMar 5, 2008
PHP min version
Downloads5K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

@reply Developer Profile

Jeff Waugh

4 plugins · 80 total installs

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

How We Detect @reply

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about @reply