Block Permissions Security & Risk Analysis

wordpress.org/plugins/block-permissions

Show Gutenberg editor blocks only to target audience depending on their user attributes such as user role, log in information and user names.

400 active installs v1.0.8 PHP 5.6+ WP 5.6.0+ Updated Oct 25, 2021
addonblockscontent-restrictiondategutenberg
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Block Permissions Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 4yr ago
Risk Assessment

The block-permissions plugin version 1.0.8 exhibits a very strong security posture based on the provided static analysis and vulnerability history. The absence of any detected entry points, dangerous functions, raw SQL queries, unescaped output, file operations, external HTTP requests, and the completeness of nonce and capability checks (or lack thereof due to no entry points) are all indicators of robust security practices. The taint analysis further supports this by showing no flows with unsanitized paths, suggesting that user input, if any were processed, would be handled safely.

Furthermore, the plugin has no recorded vulnerability history, including CVEs of any severity. This suggests a history of secure development and maintenance. While the current data paints an excellent security picture, it's important to note that the lack of detected entry points could also mean the plugin has limited functionality or is designed to be called only through specific, already secured WordPress mechanisms. This plugin appears to be exceptionally well-developed from a security perspective, with no apparent weaknesses based on the provided data.

Vulnerabilities
None known

Block Permissions Security Vulnerabilities

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

Block Permissions 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

Block Permissions Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitmcw-bp-gutenberg.php:44
actionenqueue_block_editor_assetsmcw-bp-gutenberg.php:46
actionrest_api_initmcw-bp-gutenberg.php:233
Maintenance & Trust

Block Permissions Maintenance & Trust

Maintenance Signals

WordPress version tested5.8.13
Last updatedOct 25, 2021
PHP min version5.6
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs400
Developer Profile

Block Permissions Developer Profile

meceware

2 plugins · 600 total installs

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

How We Detect Block Permissions

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/block-permissions/dist/blocks.build.js/wp-content/plugins/block-permissions/dist/blocks.editor.build.css/wp-content/plugins/block-permissions/dist/picker.min.css
Script Paths
/wp-content/plugins/block-permissions/dist/blocks.build.js/wp-content/plugins/block-permissions/dist/picker.min.css
Version Parameters
block-permissions/dist/blocks.build.js?ver=block-permissions/dist/blocks.editor.build.css?ver=block-permissions/dist/picker.min.css?ver=

HTML / DOM Fingerprints

CSS Classes
mcw-bp-gutenberg
Data Attributes
data-block-permissions
JS Globals
window.McwBPUserRolesControllerwindow.McwBPUsersController
REST Endpoints
/wp-json/meceware/block-permissions/v1/user-roles/wp-json/meceware/block-permissions/v1/users
FAQ

Frequently Asked Questions about Block Permissions