
Runkeeper Security & Risk Analysis
wordpress.org/plugins/runkeeper-pluginInserts previews of your Runkeeper activity into a post
Is Runkeeper Safe to Use in 2026?
Generally Safe
Score 85/100Runkeeper has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The 'runkeeper-plugin' v2.2 exhibits a generally good security posture based on the provided static analysis. The absence of dangerous functions, SQL queries without prepared statements, file operations, and external HTTP requests are positive indicators. Crucially, there are no logged vulnerabilities (CVEs) associated with this plugin, suggesting a history of responsible development or a lack of targeted attacks, both of which contribute to its current security standing. However, a significant concern arises from the lack of output escaping. With 100% of detected outputs not being properly escaped, this presents a substantial risk of Cross-Site Scripting (XSS) vulnerabilities, allowing attackers to inject malicious scripts into the site's content. While the attack surface is small and appears to have no direct unprotected entry points from the static analysis, the unescaped output is a critical flaw that requires immediate attention to mitigate potential security breaches.
Key Concerns
- Unescaped output detected
Runkeeper Security Vulnerabilities
Runkeeper Code Analysis
Output Escaping
Runkeeper Attack Surface
Shortcodes 1
WordPress Hooks 4
Maintenance & Trust
Runkeeper Maintenance & Trust
Maintenance Signals
Community Trust
Runkeeper Developer Profile
2 plugins · 20 total installs
How We Detect Runkeeper
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/runkeeper-plugin/runkeeper.js/wp-content/plugins/runkeeper-plugin/runkeeper.jsHTML / DOM Fingerprints
id="runkeeper"title="<div id="runkeeper"