Genki Feedburner SiteStats Security & Risk Analysis

wordpress.org/plugins/genki-feedburner-sitestats

Insert Feedburner SiteStats code (without Feeds Flare) for a speed boost

10 active installs v1.0 PHP + WP 2.0.0+ Updated Oct 9, 2010
feedburnersite-stats
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Genki Feedburner SiteStats Safe to Use in 2026?

Generally Safe

Score 85/100

Genki Feedburner SiteStats has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 15yr ago
Risk Assessment

The genki-feedburner-sitestats plugin version 1.0 presents a mixed security posture. On the positive side, the plugin has no known vulnerabilities, no dangerous functions, and all SQL queries utilize prepared statements. Furthermore, there are no external HTTP requests, file operations, or bundled libraries, which generally reduces the attack surface.

However, significant concerns arise from the static analysis. A complete lack of any authorization checks (capability checks, nonce checks) on all entry points, coupled with the fact that none of the identified output is properly escaped, creates a substantial risk. The taint analysis reveals two flows with unsanitized paths, although they are not flagged as critical or high severity. The absence of any security controls on the attack surface, combined with unescaped output, means that an attacker could potentially inject malicious code or data that would be directly rendered by the browser, leading to Cross-Site Scripting (XSS) vulnerabilities.

Given the plugin's clean vulnerability history, it might suggest either good development practices in the past or simply a lack of targeted discovery. However, the current code analysis highlights critical security gaps that are independent of historical vulnerability data. While the plugin boasts a small attack surface and robust SQL handling, the critical lack of output escaping and authorization checks for any potential entry points represents a significant weakness that could easily be exploited.

Key Concerns

  • Unescaped output found
  • No capability checks on any entry points
  • No nonce checks on any entry points
  • Flows with unsanitized paths found (taint analysis)
Vulnerabilities
None known

Genki Feedburner SiteStats Security Vulnerabilities

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

Genki Feedburner SiteStats Code Analysis

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

Output Escaping

0% escaped3 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
genki_feedburner_sitestats_manage (genki_feedburner_sitestats.php:22)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Genki Feedburner SiteStats Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionadmin_menugenki_feedburner_sitestats.php:11
actionwp_footergenki_feedburner_sitestats.php:12
Maintenance & Trust

Genki Feedburner SiteStats Maintenance & Trust

Maintenance Signals

WordPress version tested2.7.0
Last updatedOct 9, 2010
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Genki Feedburner SiteStats Developer Profile

genkisan

2 plugins · 50 total installs

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

How We Detect Genki Feedburner SiteStats

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
<script src="http://feeds.feedburner.com/~s/" type="text/javascript" charset="utf-8"></script>
FAQ

Frequently Asked Questions about Genki Feedburner SiteStats