Special Footer Links Security & Risk Analysis

wordpress.org/plugins/wc-footer-links

This is a work in progress of a plugin created to facilitate easy footer link management.

10 active installs v1.2 PHP + WP 2.7+ Updated Aug 17, 2013
footerlinks
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Special Footer Links Safe to Use in 2026?

Generally Safe

Score 85/100

Special Footer Links has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 12yr ago
Risk Assessment

The "wc-footer-links" v1.2 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits its attack surface. Furthermore, the code signals indicate no dangerous functions or raw SQL queries, with all SQL operations utilizing prepared statements, which are excellent security practices. The lack of recorded vulnerabilities in its history further suggests a well-maintained and secure plugin.

However, a significant concern arises from the output escaping metric, where 100% of the single identified output is not properly escaped. This means that any data displayed by the plugin could be vulnerable to cross-site scripting (XSS) attacks if that data originates from user input or an untrusted source. While the taint analysis shows no identified flows, this is likely due to the limited scope of the analysis or the absence of exploitable taint paths in the analyzed code. The lack of nonce and capability checks on entry points, though minimal in this case due to zero entry points, would be a critical oversight if the attack surface were larger.

In conclusion, the plugin demonstrates strengths in its minimal attack surface and secure database interactions. The primary weakness lies in the unescaped output, which presents a clear XSS risk that needs immediate attention. The absence of historical vulnerabilities is positive, but it should not overshadow the identified coding practice issue. Addressing the unescaped output is crucial to mitigate potential security risks.

Key Concerns

  • Unescaped output found
Vulnerabilities
None known

Special Footer Links Security Vulnerabilities

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

Special Footer Links Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Special Footer Links Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_footerwc-special-footer-links.php:60
Maintenance & Trust

Special Footer Links Maintenance & Trust

Maintenance Signals

WordPress version tested3.6.1
Last updatedAug 17, 2013
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Special Footer Links Developer Profile

willshouse

3 plugins · 5K total installs

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

How We Detect Special Footer Links

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

Asset Fingerprints

HTML / DOM Fingerprints

HTML Comments
<!-- live --><!-- cached -->
Shortcode Output
here1 here2 here3 here4
FAQ

Frequently Asked Questions about Special Footer Links