Merge + Minify + Refresh Check Visual Composer Security & Risk Analysis

wordpress.org/plugins/mmr-disable-for-visual-composer-editor

Disable MMR when editing a page using the Visual Composer editor.

10 active installs v1.0.0 PHP + WP 3.6.1+ Updated Mar 16, 2020
closureconcatenatemergeminifyrefresh
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Merge + Minify + Refresh Check Visual Composer Safe to Use in 2026?

Generally Safe

Score 85/100

Merge + Minify + Refresh Check Visual Composer has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 6yr ago
Risk Assessment

The 'mmr-disable-for-visual-composer-editor' v1.0.0 plugin exhibits an exceptionally strong security posture based on the provided static analysis. The absence of any detected attack surface, including AJAX handlers, REST API routes, shortcodes, or cron events, significantly minimizes the potential for external exploitation. Furthermore, the code signals are overwhelmingly positive, with no dangerous functions, all SQL queries utilizing prepared statements, and all outputs being properly escaped. The lack of file operations, external HTTP requests, and the absence of nonce and capability checks, while potentially indicative of a very simple plugin, do not present immediate risks given the zero attack surface.

The plugin's vulnerability history is also a major strength, with no known CVEs recorded. This, combined with the clean static analysis, suggests a well-developed and secure piece of code. The absence of any taint analysis findings further reinforces this positive assessment.

In conclusion, 'mmr-disable-for-visual-composer-editor' v1.0.0 appears to be a highly secure plugin. Its strengths lie in its minimal attack surface and the evident adherence to secure coding practices. The primary weakness, if it can be called that, is the lack of any discernible functionality that would necessitate the use of more robust security checks like nonces or capability checks, which is a reflection of its apparent simplicity rather than a security flaw.

Vulnerabilities
None known

Merge + Minify + Refresh Check Visual Composer Security Vulnerabilities

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

Merge + Minify + Refresh Check Visual Composer 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

Merge + Minify + Refresh Check Visual Composer Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
filtershould_mmrmerge-minify-refresh-check-visual-composer.php:38
Maintenance & Trust

Merge + Minify + Refresh Check Visual Composer Maintenance & Trust

Maintenance Signals

WordPress version tested5.4.19
Last updatedMar 16, 2020
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Merge + Minify + Refresh Check Visual Composer Developer Profile

launchinteractive

4 plugins · 5K total installs

73
trust score
Avg Security Score
92/100
Avg Patch Time
737 days
View full developer profile
Detection Fingerprints

How We Detect Merge + Minify + Refresh Check Visual Composer

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 Merge + Minify + Refresh Check Visual Composer