Marc Armengou

PlugSeal gives administrators granular control over what each active plugin is allowed to do, inspired by Android app permissions and Flatseal for Flatpak. Each active plugin is listed in the settings page. For each plugin, administrators can allow or deny individual permissions with immediate effect. All permissions are allowed by default, so no existing functionality is broken until an administrator explicitly restricts it.
Permissions covered:
<ul>
<li><code>db:read</code> / <code>db:write</code> — database queries via $wpdb</li>
<li><code>db:read:users</code> / <code>db:write:users</code> — read and write access to user data (also covers wp_delete_user and wp_update_user)</li>
<li><code>http:outbound</code> — outbound HTTP requests via the WordPress HTTP API</li>
<li><code>options:read</code> / <code>options:write</code> — WordPress options via get_option / update_option (see limitations)</li>
<li><code>email:send</code> — sending email via wp_mail()</li>
<li><code>cron:write</code> — scheduling events via wp_schedule_event()</li>
<li><code>transients:write</code> — writing transients via set_transient()</li>
<li><code>users:create</code> — creating users via wp_create_user() (deletes are covered by db:write:users)</li>
<li><code>rest:register</code> — registering REST API endpoints via register_rest_route()</li>
<li><code>shortcode:register</code> — registering shortcodes via add_shortcode()</li>
<li><code>rewrite:register</code> — registering rewrite rules via add_rewrite_rule()</li>
<li><code>admin:menu</code> — adding entries to the admin menu and submenus</li>
<li><code>dashboard:widget</code> — adding dashboard widgets via wp_add_dashboard_widget()</li>
<li><code>hooks:frontend</code> — hooking into frontend hooks (wp_head, wp_footer, the_content, wp_enqueue_scripts…)</li>
<li><code>hooks:admin</code> — hooking into admin hooks (admin_head, admin_notices, admin_enqueue_scripts…)</li>
<li><code>hooks:auth</code> — hooking into authentication hooks (wp_login, wp_logout, user_register, authenticate…)</li>
<li><code>hooks:content</code> — hooking into content hooks (save_post, delete_post, pre_get_posts, wp_handle_upload…)</li>
<li><code>hooks:lifecycle</code> — hooking into plugin and theme lifecycle hooks (activated_plugin, deactivated_plugin, switch_theme…)</li>
</ul>
Honest limitations:
This plugin intercepts official WordPress APIs by identifying the calling plugin via the PHP call stack. It cannot intercept calls made by WordPress core on behalf of a plugin — for example, when WordPress processes a settings form via <code>options.php</code>, the call stack contains core files rather than the plugin files.
Specific limitations:
<ul>
<li><code>options:read</code> / <code>options:write</code> — work when a plugin calls these APIs directly from its own code (hooks, AJAX, cron). Do not block standard WordPress settings forms processed by <code>options.php</code>.</li>
<li>Filesystem access (<code>file_get_contents</code>, <code>fopen</code>, etc.) is not intercepted.</li>
<li>Direct <code>mysqli</code> connections, <code>eval()</code>, and raw PHP file functions bypass all interceptors.</li>
<li><code>wp_update_user()</code> and <code>wp_delete_user()</code> are covered by <code>db:write:users</code> since they write directly to the users table.</li>
<li><code>admin_init</code> is intentionally excluded from <code>hooks:admin</code> as it is too critical to block safely.</li>
</ul>

PlugSeal

Control what each active plugin is allowed to do. Allow or deny specific permissions per plugin, with immediate effect.

Rafal Gierlicki

NETSENSAI Shield offers a range of security features, including:
Changing the login URL to reduce brute force attack risks.
Disabling the REST API (WP API JSON) for non-logged-in users.
Disabling XML-RPC to prevent unauthorized access.
Disabling the WordPress file editor to avoid accidental or malicious changes.
Disabling Application Passwords to block unauthorized API access.
Applying advanced HTTP security headers (e.g., HSTS, X-Frame-Options, Content-Security-Policy).
Integration with W3 Total Cache:
Permanently disable .htaccess writes by W3TC
Runtime disabling of Page Cache UI
One-time full cache flush on first admin page load
Automatic cache flush on Secure Options save
Physical cleanup and permanent disable via the W3TC API
Suppression of Site Health REST API availability notices for non-logged-in users (removes false Site Health errors while maintaining full API blocking).
In addition, the plugin provides helpful user feedback:
Email notifications when the login URL changes – sends a localized HTML email (Polish or English) with your old and new login links, change date and the plugin logo, so you remember to update your bookmarks.
Admin popup when disabling the WP API JSON – displays a friendly modal warning that disabling the REST API may break plugins like WooCommerce or contact forms. The popup includes a purchase link to upgrade to the PRO version if you need this feature without losing functionality.
Scoped styling – the custom colour for the “Save changes” button is now limited to the Secure Options page, so other admin pages keep the default WordPress look.
Promotional banner assistant – notifies administrators of summer discount codes and NETSENSAI Shield PRO features.
The free version provides both core and advanced Level 3 security functionalities. A PRO version offers extended support, additional features, and automatic protection enhancements.

NETSENSAI Shield

Hardens and protects your site by locking down login, REST API, XML‑RPC, file editor, and applying HTTP security headers.

PlugSeal vs NETSENSAI Shield