Marc Armengou

<p>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.</p>
<p><strong>Permissions covered:</strong></p>
<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>
<p><strong>Honest limitations:</strong></p>
<p>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.</p>
<p>Specific limitations:</p>
<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.

sweetwatermedia

<p>Steel Security & Hardening – Site Audit Tools focuses on practical security hygiene for WordPress administrators.</p>
<p>The free plugin provides:</p>
<ul>
<li>on-demand security scans</li>
<li>risk summaries grouped by severity and category</li>
<li>checks for common WordPress hardening gaps</li>
<li>checks for exposed root-level artifacts such as <code>.env</code>, SQL dumps, <code>phpinfo</code> files, and backup archives</li>
<li>a quarantine vault for operator-reviewed file isolation</li>
<li>uploads PHP execution blocking on supported server environments</li>
<li>manual guidance when automatic server hardening is not safely supported</li>
</ul>
<p>This plugin is positioned as an auditing and hardening tool. It helps surface risk and apply selected preventive controls, but it does not promise malware removal, incident response, or complete server protection.</p>
<h4>Included checks</h4>
<p>The scan currently looks for items such as:</p>
<ul>
<li>PHP error display exposure</li>
<li><code>WP_DEBUG</code> and <code>debug.log</code> exposure</li>
<li>XML-RPC availability</li>
<li>author and REST user enumeration exposure</li>
<li>theme/plugin file editor availability</li>
<li>WordPress generator meta output</li>
<li>comments enabled by default</li>
<li>uploads PHP execution hardening status</li>
<li>root-level sensitive files and archives</li>
</ul>
<h4>Server-aware behavior</h4>
<p>This plugin only auto-applies server config changes where it can do so in a scoped and reversible way.</p>
<ul>
<li>Apache and LiteSpeed: uploads PHP blocking is managed through a Steel Security-marked <code>.htaccess</code> block</li>
<li>IIS: uploads PHP blocking is managed through a Steel Security-marked <code>web.config</code> section</li>
<li>Nginx and unsupported environments: Steel Security provides manual guidance instead of claiming automatic protection</li>
</ul>
<h4>Pro companion</h4>
<p>This plugin can work with a separate Pro companion plugin that adds features such as scheduled scans, scan history, reports, and managed server-level controls such as directory listing protection and baseline security headers. The free plugin remains usable on its own.</p>


Steel Security & Hardening – Site Audit Tools

High-signal WordPress security auditing and hardening with practical site audit tools for administrators.

PlugSeal vs Steel Security & Hardening – Site Audit Tools