PageRank Security & Risk Analysis

wordpress.org/plugins/pagerank

Displays Google PageRank in the sidebar of your blog via widget interface or anywhere else via function call.

10 active installs v0.4 PHP + WP 2.5+ Updated Unknown
googlepagerankstatisticsstats
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is PageRank Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The 'pagerank' plugin version 0.4 presents a mixed security posture. On the positive side, it has no recorded vulnerabilities, no external HTTP requests, and all its SQL queries use prepared statements, indicating good practices in these areas. The static analysis shows a very limited attack surface with no exposed AJAX handlers, REST API routes, shortcodes, or cron events that are not properly secured. However, significant concerns arise from the code analysis. The presence of the `create_function` is a notable risk as it can lead to arbitrary code execution if not handled with extreme care, and its usage here is not mitigated by other security checks. Furthermore, a low rate of output escaping (27%) suggests a high likelihood of cross-site scripting (XSS) vulnerabilities, as user-supplied data is likely being rendered without proper sanitization.

Key Concerns

  • Use of dangerous function: create_function
  • Low output escaping rate (27%)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

PageRank Security Vulnerabilities

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

PageRank Code Analysis

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

Dangerous Functions Found

create_functionadd_action('plugins_loaded', create_function('$PageRank_sd2121c', 'global $PageRank; $PageRank = newpagerank.php:295

Output Escaping

27% escaped15 total outputs
Attack Surface

PageRank Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menupagerank.php:100
actionwp_headpagerank.php:103
actionwidgets_initpagerank.php:106
actionplugins_loadedpagerank.php:295
Maintenance & Trust

PageRank Maintenance & Trust

Maintenance Signals

WordPress version tested4.0.38
Last updatedUnknown
PHP min version
Downloads6K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

PageRank Developer Profile

tomknows

2 plugins · 20 total installs

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

How We Detect PageRank

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/pagerank/img/0.gif/wp-content/plugins/pagerank/img/1.gif/wp-content/plugins/pagerank/img/2.gif/wp-content/plugins/pagerank/screenshot-1.gif/wp-content/plugins/pagerank/screenshot-2.gif/wp-content/plugins/pagerank/screenshot-3.gif
Generator Patterns
pagerank/pagerank.php
Version Parameters
pagerank/pagerank.php?ver=

HTML / DOM Fingerprints

CSS Classes
snap_noshots
Shortcode Output
<div id="pagerank"><a class="snap_noshots" href="https://profiles.wordpress.org/tomknows/" target="_blank"><img src="" border="0" alt="Pagerank" title="Pagerank" /></a><br /><small>Plugin by <a href="https://profiles.wordpress.org/tomknows/" class="snap_noshots" target="_blank">Tom</a></small></div>
FAQ

Frequently Asked Questions about PageRank