mypace Remove Comments Feed Link Security & Risk Analysis

wordpress.org/plugins/mypace-remove-comments-feed-link

This plugin will remove comments feed links from header, output only posts feed.

100 active installs v1.1.1 PHP + WP 4.0+ Updated Dec 12, 2020
commentsfeedrss
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is mypace Remove Comments Feed Link Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

The "mypace-remove-comments-feed-link" plugin v1.1.1 exhibits a strong security posture based on the provided static analysis. The plugin has no known CVEs, indicating a clean vulnerability history. The static analysis reveals a minimal attack surface with zero entry points, including no AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, the code adheres to good practices by not utilizing dangerous functions, performing SQL queries exclusively with prepared statements, and having no file operations or external HTTP requests.

However, a significant concern arises from the output escaping analysis. With one total output identified and 0% properly escaped, this indicates a potential for Cross-Site Scripting (XSS) vulnerabilities. Any output generated by the plugin that is not correctly escaped could be manipulated by an attacker to inject malicious scripts. The absence of nonce and capability checks, while less concerning given the limited attack surface, still represents a missed opportunity for enhanced security, especially if future versions were to expand functionality.

In conclusion, while the plugin demonstrates excellent foundational security by minimizing its attack surface and avoiding common pitfalls like raw SQL queries, the unescaped output is a critical weakness that requires immediate attention. The lack of any recorded vulnerabilities in its history is a positive sign, but it doesn't negate the identified risk in the current version's code.

Key Concerns

  • Output not properly escaped
Vulnerabilities
None known

mypace Remove Comments Feed Link Security Vulnerabilities

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

mypace Remove Comments Feed Link Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

mypace Remove Comments Feed Link Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
filterfeed_links_show_comments_feedmypace-remove-comments-feed-link.php:17
filterwp_headmypace-remove-comments-feed-link.php:27
filterpost_comments_feed_linkmypace-remove-comments-feed-link.php:35
actionparse_querymypace-remove-comments-feed-link.php:47
actionplugins_loadedmypace-remove-comments-feed-link.php:53
Maintenance & Trust

mypace Remove Comments Feed Link Maintenance & Trust

Maintenance Signals

WordPress version tested5.6.17
Last updatedDec 12, 2020
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings2
Active installs100
Developer Profile

mypace Remove Comments Feed Link Developer Profile

けい (Kei Nomura)

3 plugins · 3K total installs

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

How We Detect mypace Remove Comments Feed Link

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
<link rel="alternate" type="rss2" title="My Blog &raquo; RSS 2.0 Feed" href="http://example.com/feed/" />
FAQ

Frequently Asked Questions about mypace Remove Comments Feed Link