Revisioner Security & Risk Analysis

wordpress.org/plugins/revisioner

Clears all revisions from your database.

10 active installs v1.0.1 PHP + WP 2.8+ Updated Aug 9, 2012
pagespostsrevisions
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Revisioner Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The "revisioner" plugin version 1.0.1 demonstrates a generally strong security posture based on the provided static analysis. There are no identified dangerous functions, file operations, or external HTTP requests. The single SQL query utilizes prepared statements, indicating good database interaction practices. Output escaping is also well-implemented, with only a small percentage of outputs potentially unescaped, which is a minor concern but not critical.

The absence of any identified CVEs and vulnerability history is a significant positive indicator, suggesting the plugin has historically been maintained securely or has not been a target for significant exploits. The plugin also presents a minimal attack surface, with no AJAX handlers, REST API routes, shortcodes, or cron events, further reducing the potential for external manipulation.

However, a notable concern is the complete lack of nonce checks and capability checks across any potential entry points. While the current static analysis shows no entry points, this indicates a potential weakness if any are introduced in future versions or if the analysis did not cover all possible interaction vectors. The 90% output escaping, while good, still leaves a small percentage that could be susceptible to cross-site scripting (XSS) vulnerabilities if sensitive data is outputted without proper sanitization. Overall, "revisioner" appears to be a relatively safe plugin, but the lack of input validation and capability checks warrants careful monitoring.

Key Concerns

  • No nonce checks on potential entry points
  • No capability checks on potential entry points
  • 10% of output potentially unescaped
Vulnerabilities
None known

Revisioner Security Vulnerabilities

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

Revisioner Code Analysis

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

SQL Query Safety

100% prepared1 total queries

Output Escaping

90% escaped10 total outputs
Attack Surface

Revisioner Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionadmin_menurevisioner.php:178
Maintenance & Trust

Revisioner Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedAug 9, 2012
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Revisioner Developer Profile

Lopo Lencastre de Almeida

8 plugins · 150 total installs

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

How We Detect Revisioner

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/revisioner/

HTML / DOM Fingerprints

Data Attributes
name="revisions"name="autosave"name="clearall"name="info_update"
FAQ

Frequently Asked Questions about Revisioner