Block Plugin Update Security & Risk Analysis

wordpress.org/plugins/block-specific-plugin-updates

This plugin blocks the updates for specific plugins. You can select the plugins from plugin setting page.

6K active installs v3.3.2 PHP + WP 3.0+ Updated Nov 26, 2024
block-plugin-updatedisable-plugin-updatehide-plugin-update-notificationplugin-update-hider
92
A · Safe
CVEs total1
Unpatched0
Last CVESep 27, 2023
Safety Verdict

Is Block Plugin Update Safe to Use in 2026?

Generally Safe

Score 92/100

Block Plugin Update has a strong security track record. Known vulnerabilities have been patched promptly.

1 known CVELast CVE: Sep 27, 2023Updated 1yr ago
Risk Assessment

The "block-specific-plugin-updates" plugin, version 3.3.2, exhibits a generally positive security posture with a commendable lack of critical vulnerabilities detected in static analysis. Its attack surface is minimal, with no exposed AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, none of these entry points are unprotected. The code also demonstrates good practices by exclusively using prepared statements for SQL queries and including a nonce check. However, a significant concern arises from the low rate of output escaping (20%), indicating a potential for reflected or stored cross-site scripting (XSS) vulnerabilities if user-supplied data is not properly sanitized before being displayed. The presence of one past medium severity vulnerability (CSRF) in its history, while currently patched, suggests that the plugin has had security issues in the past, emphasizing the need for continued vigilance and timely updates.

Key Concerns

  • Low output escaping rate
  • Past medium vulnerability (CSRF)
Vulnerabilities
1

Block Plugin Update Security Vulnerabilities

CVEs by Year

1 CVE in 2023
2023
Patched Has unpatched

Severity Breakdown

Medium
1

1 total CVE

CVE-2023-44261medium · 5.3Cross-Site Request Forgery (CSRF)

Block Plugin Update <= 3.3.1 - Cross-Site Request Forgery via bspu_plugin_select.php

Sep 27, 2023 Patched in 3.3.2 (118d)
Code Analysis
Analyzed Mar 16, 2026

Block Plugin Update Code Analysis

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

Output Escaping

20% escaped5 total outputs
Data Flows
All sanitized

Data Flow Analysis

1 flows
<bspu_plugin_select> (includes\bspu_plugin_select.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Block Plugin Update Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
filterhttp_request_argsblock-specific-plugin-updates.php:27
actionadmin_menuplugin_interface.php:3
actionadmin_initplugin_interface.php:11
Maintenance & Trust

Block Plugin Update Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedNov 26, 2024
PHP min version
Downloads105K

Community Trust

Rating88/100
Number of ratings19
Active installs6K
Developer Profile

Block Plugin Update Developer Profile

Dnesscarkey

5 plugins · 535K total installs

76
trust score
Avg Security Score
96/100
Avg Patch Time
474 days
View full developer profile
Detection Fingerprints

How We Detect Block Plugin Update

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/block-specific-plugin-updates/plugin_interface.php

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Block Plugin Update