Monkeyman Rewrite Analyzer Security & Risk Analysis

wordpress.org/plugins/monkeyman-rewrite-analyzer

Making sense of the rewrite mess. Display and play with your rewrite rules.

2K active installs v1.0 PHP + WP 3.0+ Updated May 12, 2011
debugdevelopmentmod_rewritepermalinksrewrite
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Monkeyman Rewrite Analyzer Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 14yr ago
Risk Assessment

The "monkeyman-rewrite-analyzer" v1.0 plugin exhibits an excellent security posture based on the provided static analysis. The complete absence of identified attack surface points, dangerous functions, raw SQL queries, file operations, external HTTP requests, and taint flows with unsanitized paths is a strong indicator of robust coding practices and a low risk of exploitation through common web vulnerabilities. Furthermore, the lack of any recorded CVEs or past vulnerabilities in its history reinforces this positive assessment, suggesting a stable and secure codebase over time.

Despite the overall positive findings, there is a minor concern regarding output escaping. With 5 total outputs and only 20% properly escaped, there is a significant opportunity for cross-site scripting (XSS) vulnerabilities if the unescaped outputs contain user-controlled or dynamic data. While the static analysis didn't flag specific taint flows leading to these outputs, it's a potential area for improvement. The absence of capability and nonce checks, while not directly flagged as a risk due to the lack of an attack surface, would become a critical concern if any entry points were to be introduced in future versions.

Key Concerns

  • Unescaped output detected
Vulnerabilities
None known

Monkeyman Rewrite Analyzer Security Vulnerabilities

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

Monkeyman Rewrite Analyzer Code Analysis

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

Output Escaping

20% escaped5 total outputs
Attack Surface

Monkeyman Rewrite Analyzer Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actioninitinclude\class-monkeyman-rewrite-analyzer.php:36
actionadmin_menuinclude\class-monkeyman-rewrite-analyzer.php:37
filtercontextual_helpinclude\class-monkeyman-rewrite-analyzer.php:52
actionplugins_loadedrewrite-analyzer.php:53
Maintenance & Trust

Monkeyman Rewrite Analyzer Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedMay 12, 2011
PHP min version
Downloads73K

Community Trust

Rating100/100
Number of ratings26
Active installs2K
Developer Profile

Monkeyman Rewrite Analyzer Developer Profile

Jan Fabry

1 plugin · 2K total installs

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

How We Detect Monkeyman Rewrite Analyzer

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/monkeyman-rewrite-analyzer/rewrite-analyzer.css/wp-content/plugins/monkeyman-rewrite-analyzer/rewrite-analyzer.js
Script Paths
/wp-content/plugins/monkeyman-rewrite-analyzer/rewrite-analyzer.js
Version Parameters
monkeyman-rewrite-analyzer/rewrite-analyzer.css?ver=monkeyman-rewrite-analyzer/rewrite-analyzer.js?ver=

HTML / DOM Fingerprints

CSS Classes
regexgroup-target-value
Data Attributes
id="regex-data-regex-group-id="
JS Globals
Monkeyman_Rewrite_Analyzer_Regexes
FAQ

Frequently Asked Questions about Monkeyman Rewrite Analyzer