Gutenbye Security & Risk Analysis

wordpress.org/plugins/gutenbye

A very simple plugin to disable the Block Editor (formerly known as Gutenberg) and restore the classic WordPress editing experience.

800 active installs v1.0.0 PHP 7.1+ WP 4.6+ Updated Dec 7, 2018
blockclassiceditorgutenberg
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Gutenbye Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'gutenbye' plugin v1.0.0 exhibits a strong security posture. The absence of any identified attack surface points, dangerous functions, raw SQL queries, unescaped outputs, file operations, or external HTTP requests suggests a very well-secured codebase. The complete lack of vulnerability history further reinforces this assessment, indicating no previously discovered security flaws. This level of security is commendable and suggests diligent development practices.

However, the complete absence of nonce checks and capability checks across all entry points is a notable area of concern. While the current attack surface is zero, this implies that if any new entry points were introduced or discovered, they would be inherently unprotected. This lack of fundamental WordPress security checks presents a latent risk. The plugin's security is entirely dependent on the current minimal attack surface remaining so. A balanced conclusion is that 'gutenbye' v1.0.0 is currently very secure due to its clean code and lack of history, but it lacks inherent security hardening for potential future expansions or unforeseen vulnerabilities.

Key Concerns

  • Missing nonce checks on potential entry points
  • Missing capability checks on potential entry points
Vulnerabilities
None known

Gutenbye Security Vulnerabilities

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

Gutenbye Code Analysis

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

Gutenbye Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
filteruse_block_editor_for_post_typegutenbye.php:19
Maintenance & Trust

Gutenbye Maintenance & Trust

Maintenance Signals

WordPress version tested5.0.25
Last updatedDec 7, 2018
PHP min version7.1
Downloads6K

Community Trust

Rating0/100
Number of ratings0
Active installs800
Developer Profile

Gutenbye Developer Profile

Chris Lanphear

1 plugin · 800 total installs

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

How We Detect Gutenbye

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Gutenbye