Disable Gutenberg (v3.3) is a lightweight, highly configurable plugin that removes the Gutenberg/Block Editor and restores the classic WordPress editing experience (TinyMCE, meta boxes, custom fields, quicktags, and the original “Edit Post” screen). It’s widely used by site owners who rely on legacy workflows, Classic Editor-compatible extensions, or page builders like Elementor/Composer—and it does so without collecting user data, setting cookies, or calling third-party services. With Plugin Security Certification (PSC-2026-64601) by CleanTalk, Disable Gutenberg is now formally verified not only for performance and compatibility, but also for secure coding practices and resilience against modern WordPress plugin attack vectors.
| Name of | Disable Gutenberg |
| Version | 3.3 |
| Downloads | 600 000+ |
| Description | Disable Gutenberg Block Editor and restore the Classic Editor and original Edit Post screen (TinyMCE, meta boxes, etc.). |
| Security | Successfully tested for: SQL Injection (SQLi) Cross-Site Scripting (XSS) – Stored & Reflected Cross-Site Request Forgery (CSRF) Authentication Vulnerabilities Authentication Bypass Exploits Privilege Escalation Buffer Overflow Denial-of-Service (DoS) vectors Data Leakage Vulnerabilities Insecure Dependency Usage Remote Code Execution (RCE) Risks Unauthorized File Access Insufficient Injection Protection Information Disclosure via Misconfigured Endpoints |
| CleanTalk Certification | Proudly earned the “Plugin Security Certification” (PSC) from CleanTalk, indicating adherence to stringent security standards. |
| Additional Information | Users can confidently manage age restrictions with the assurance of the “Plugin Security Certification” (PSC). Verify the latest details on the plugin developer’s website. |
| Plugin Security Certification by CleanTalk |  |
| Logo of the plugin |  |
PSC by CleantalkJoin the community of developers who prioritize security. Highlight your plugin in the WordPress catalog.
Key Features
Full Gutenberg Control (Global or Granular)
Disable Gutenberg can turn off the Block Editor entirely or selectively depending on your site requirements:
- Disable Gutenberg for all post types
- Disable Gutenberg for specific post types
- Disable Gutenberg for specific user roles
- Disable Gutenberg for theme templates
- Disable Gutenberg for specific post/page IDs
- Whitelist by post title, slug, or ID
- Choose which editor to use per post
Classic Editor Restoration and UX Enhancements
The plugin doesn’t just “turn off Gutenberg”—it restores key classic workflows:
- Restores TinyMCE, classic meta boxes, custom fields, quicktags, etc.
- Adds “Classic Editor” link to each post in the Posts list
- Adds “Add New (Classic)” to the WP admin menu
- Option to enable/disable frontend Gutenberg stylesheet
- Option to disable block-based widgets and restore Classic Widgets
- Option to hide Gutenberg-related UI elements (nag notices, menu items, etc.)
- One-click restore of plugin defaults
Built for Compatibility and Performance
Disable Gutenberg is intentionally focused and efficient:
- Built using WordPress APIs
- Designed to be fast and low-impact on server resources
- Works well alongside other plugins and builders
- Translation-ready and regularly updated to remain stable across WordPress versions
- Works well with AMP solutions (including the WordPress AMP plugin)
Security Assurance
Disable Gutenberg v3.3 has achieved CleanTalk Plugin Security Certification (PSC-2026-64601), confirming the plugin’s security posture through review and testing aligned with high-risk WordPress plugin threat models. As part of certification, it was:
The plugin has been successfully tested for:
✅ Information Leakage Vulnerabilities
✅ SQL Injection Vulnerabilities
✅ Cross-Site Scripting (XSS) Attacks
✅ Cross-Site Request Forgery (CSRF) Attacks
✅ Authentication & Authentication Bypass Vulnerabilities
✅ Privilege Escalation Vulnerabilities
✅ Buffer Overflow Vulnerabilities
✅ Denial-of-Service (DoS) Vulnerabilities
✅ Data Leakage Vulnerabilities
✅ Insecure Dependencies
✅ Code Execution Vulnerabilities
✅ File Unauthorized Access Vulnerabilities
✅ Insufficient Injection Protection
A plugin that changes editor behavior touches admin UX, editor routing, capability boundaries, and sometimes template selection logic – all areas where subtle mistakes can lead to CSRF-able settings changes, unauthorized role impacts, or information exposure via admin screens. PSC certification indicates that Disable Gutenberg’s implementation is hardened for these scenarios, including safe handling of admin actions and configuration options.
Conclusion
Disable Gutenberg (v3.3) is a practical, security-verified choice for teams that need a stable Classic Editor workflow, compatibility with legacy meta boxes and plugins, and precise control over where Gutenberg is enabled. With PSC-2026-64601 certification from CleanTalk, site owners get both: the editing experience they want and the assurance that the plugin has been vetted against major vulnerability classes – making it a safe, low-friction foundation for classic WordPress content operations.
Note: The date and certification information may change over time. It is advisable to verify the latest details on the plugin developer’s website.