Blocksify – Gutenberg blocks by PressMaximum Security & Risk Analysis

wordpress.org/plugins/blocksify

Add more blocks with advanced settings for Gutenberg - Blocks Editor.

0 active installs v0.1.0 PHP 7.0+ WP 5.8+ Updated Unknown
blockgutenberggutenberg-blockspost-sectionrow
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Blocksify – Gutenberg blocks by PressMaximum Safe to Use in 2026?

Generally Safe

Score 100/100

Blocksify – Gutenberg blocks by PressMaximum has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs
Risk Assessment

The plugin "blocksify" v0.1.0 demonstrates a strong security posture based on the provided static analysis. There are no identified attack vectors such as AJAX handlers, REST API routes, shortcodes, or cron events, meaning the plugin has no exposed entry points. Furthermore, the code signals indicate a complete absence of dangerous functions, file operations, external HTTP requests, and a perfect record of using prepared statements for SQL queries and properly escaping all output. The lack of any reported vulnerabilities, historical or current, further reinforces this positive assessment. However, the complete absence of nonce checks and capability checks across all potential, albeit currently non-existent, entry points represents a potential area for future concern should the plugin's functionality expand to include any form of user interaction or data modification without proper authorization or validation mechanisms in place. This, combined with the absence of any taint analysis results (which can sometimes indicate that the analysis itself might not have found any complex flows to analyze, rather than an absolute absence of risk in larger codebases), suggests the current version is highly secure due to its limited scope and implementation.

Key Concerns

  • No nonce checks implemented
  • No capability checks implemented
Vulnerabilities
None known

Blocksify – Gutenberg blocks by PressMaximum Security Vulnerabilities

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

Blocksify – Gutenberg blocks by PressMaximum 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

Blocksify – Gutenberg blocks by PressMaximum Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actioninitblocksify.php:43
actionenqueue_block_editor_assetsblocksify.php:46
filterrender_blockblocksify.php:84
actioninitblocksify.php:99
Maintenance & Trust

Blocksify – Gutenberg blocks by PressMaximum Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedUnknown
PHP min version7.0
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Blocksify – Gutenberg blocks by PressMaximum Developer Profile

PressMaximum

4 plugins · 31K total installs

78
trust score
Avg Security Score
98/100
Avg Patch Time
117 days
View full developer profile
Detection Fingerprints

How We Detect Blocksify – Gutenberg blocks by PressMaximum

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/blocksify/build/plugins.css
Script Paths
/wp-content/plugins/blocksify/build/plugins.js
Version Parameters
pm-blocks-pluginspm-block-plugins

HTML / DOM Fingerprints

Data Attributes
pm_style
REST Endpoints
/wp-json/wp/v2/types/(?P<type>[a-z0-9_\-]+)
FAQ

Frequently Asked Questions about Blocksify – Gutenberg blocks by PressMaximum