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.

shasha310

Harden your web applications.
HTTP header fields are components of the header section of request and response messages. The headers define the operating parameters of an HTTP transaction.
Securing HTTP headers will improve the resilience of your web application against many common attacks including those that are on the OWASP top 10 list.
Securing headers can also improve your SEO rank and in addition to preventing websites from being marked as dangerous by browsers and antivirus applications.
Protect sensitive user information and be compliant with privacy regulations. Defend users from stealing private data by protecting website cookies. Use the proper directive such as “secure”, “httponly” and “samesite”, all of those will be applied automatically by “Secure HTTP Headers” plugin.
Secure HTTP Headers will automatically analyze any website and will build up secure headers directives, by the latest best practice.
In addition, Secure HTTP Headers offers fully configurable options, apply or skip any header directive as needed.
Install and activate Secure HTTP Headers with full confidence, the deactivation of this plugin will return your website header directives to their original state.
<h3>Main plugin functionality</h3>
<ol>
<li>
HTTP Strict Transport Security – helps to protect websites against man-in-the-middle attacks and cookie hijacking
</li>
<li>
X-Frame-Options – helps to protect users against ClickJacking attacks
</li>
<li>
X-Content-Type-Options – helps to prevent the browser from MIME-sniffing
</li>
<li>
Referrer-Policy – helps to control how much referrer information should be included with requests
</li>
<li>
Clear-Site-Data – helps to ensure that data is deleted from the browser if the user logs out
</li>
<li>
X-Download-Options – helps to control how IE 8 will handle downloaded HTML files
</li>
<li>
Access-Control-Allow-Origin – helps to ensure whether the response can be shared with requesting code from the given origin
</li>
<li>
Cross-Origin-Embedder-Policy – helps to prevent a document from loading any cross-origin resources that don’t explicitly grant the document permission
</li>
<li>
Permissions-Policy – helps to allow and deny the use of browser features in its own frame, and in content within any iframe elements in the document
</li>
<li>
Cross-Origin-Opener-Policy – helps to protect websites against a set of cross-origin attacks dubbed XS-Leaks
</li>
<li>
Cross-Origin-Resource-Policy – helps to protect websites against speculative side-channel attacks, like Spectre, as well as Cross-Site Script Inclusion attacks
</li>
<li>
X-Permitted-Cross-Domain-Policies – helps to control how cross-domain requests from Flash and PDF documents are handled
</li>
<li>
Cookie Http-Only flag – helps to protect websites against Cross-Site Scripting, or XSS attacks
</li>
<li>
Cookie Secure flag – helps to ensure that cookie is sent over a secure connection
</li>
<li>
Cookie Samesite Lax flag – helps to protect websites against CSRF and XSSI attacks
</li>
<li>
Expect-CT – helps to prevent the use of misissued certificates for a website. Note: The Expect-CT will likely become obsolete in June 2021
</li>
</ol>
<h3>What are the optional extras?</h3>
Magnisec is offering “Secure HTTP Headers enhanced”
A plugin that contains, in addition, an engine that watches and builds in any website changes a CSP – Content Security Policy that is best practice and recommended by all professional securities experts, that mitigate XSS -Cross site Scripting, one of the most common and destructive attacks.
Price: 50$ /year for a domain.
More details and installation <a href="https://magnisec.com" rel="nofollow ugc">here</a>

Secure HTTP Headers

Secure HTTP headers - Essential, and easy.

PlugSeal vs Secure HTTP Headers