Mobile blocks Security & Risk Analysis

wordpress.org/plugins/mobile-blocks

Need some help with the mobile website experience? Need to keep your mobile visitors engaged? Need to increase your shop website sales conversion?

0 active installs v1.2.1 PHP 5.6+ WP 4.4+ Updated Mar 27, 2022
blockslayoutmobileresponsivewoocommerce
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Mobile blocks Safe to Use in 2026?

Generally Safe

Score 85/100

Mobile blocks 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 "mobile-blocks" plugin version 1.2.1 demonstrates a generally good security posture based on the provided static analysis and vulnerability history. The absence of any identified vulnerabilities in its history, coupled with the static analysis showing no dangerous functions, SQL queries without prepared statements, file operations, or external HTTP requests, suggests a well-maintained and potentially secure codebase. The plugin also has a limited attack surface, with no entry points identified that lack authentication or permission checks. The taint analysis also revealed no issues, indicating that potentially malicious data is not being passed unsanitized through the analyzed code paths. However, a significant concern arises from the output escaping. With 33% of outputs properly escaped, this leaves a considerable portion potentially vulnerable to cross-site scripting (XSS) attacks. While the plugin has no known CVEs, this weakness in output sanitization could be a vector for future vulnerabilities. The bundling of Freemius v1.0, while not explicitly flagged as an issue in this data, warrants attention for potential out-of-date library risks in a real-world scenario, though without version specifics for the library, it's hard to quantify a direct deduction.

Key Concerns

  • Low output escaping rate
Vulnerabilities
None known

Mobile blocks Security Vulnerabilities

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

Mobile blocks Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
4
2 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
1

Bundled Libraries

Freemius1.0

Output Escaping

33% escaped6 total outputs
Attack Surface

Mobile blocks Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
filterwp_headincludes\class-wp-mobile-blocks-core.php:17
actionadmin_menuincludes\class-wp-mobile-blocks-options.php:15
actionafter_uninstallmobile-blocks.php:45
actioncustomize_registermobile-blocks.php:53
actionwp_footermobile-blocks.php:109
actionwp_enqueue_scriptsmobile-blocks.php:111
Maintenance & Trust

Mobile blocks Maintenance & Trust

Maintenance Signals

WordPress version tested5.9.13
Last updatedMar 27, 2022
PHP min version5.6
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Mobile blocks Developer Profile

Rui Guerreiro

4 plugins · 180K total installs

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

How We Detect Mobile blocks

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/mobile-blocks/css/mobile-blocks.css
Version Parameters
mobile-blocks/css/mobile-blocks.css?ver=

HTML / DOM Fingerprints

CSS Classes
mblocks-corner-button
Data Attributes
id="mobile-blocks-css"
Shortcode Output
<div class="mblocks-corner-button"> <a href="
FAQ

Frequently Asked Questions about Mobile blocks