zackdesign

AliasIO

MJP Security Tools is a focused hardening plugin that does four things well:
<ul>
<li>XSS Database Scanner — scans every table for <code><script></code>, <code><iframe></code>, <code>onclick</code>, <code>javascript:</code> and other injection patterns</li>
<li>POST Request Log — records all POST data (passwords masked) with IP, user agent, and URL for CSRF/audit detection</li>
<li>Failed Login Log — tracks every failed login attempt with username, IP, and timestamp</li>
<li>File Permission Checker — verifies WordPress root files and directories have safe permissions, checks for missing <code>index.html</code> files and SVN working copies</li>
</ul>
What this plugin does NOT do (because WordPress core already handles it):
<ul>
<li>SSL enforcement — use <code>FORCE_SSL_ADMIN</code> or let WordPress 5.7+ auto-redirect</li>
<li>Password strength — WordPress core enforces strong passwords since 4.3</li>
<li>Login rate limiting — use a dedicated plugin like Limit Login Attempts Reloaded</li>
<li>Version number hiding — marginal benefit, not worth the complexity</li>
</ul>
Upgrading from v1.x:
<ul>
<li>The admin page has moved from jQuery UI tabs to native WordPress nav tabs</li>
<li>SSL forcing, password enforcement, login throttling, version hiding, admin username changing, database prefix randomization, password reset, and .htaccess generation have been removed — WordPress core and dedicated security plugins handle these better</li>
<li>PHP sessions replaced with WP transients for flash messages</li>
<li>Log data is now stored as JSON instead of serialized PHP</li>
<li>The Javacrypt client-side crypt(3) script has been removed</li>
</ul>

MJP Security Tools

Lightweight WordPress hardening — XSS database scanner, POST request logging, failed login logging, and file permission checker.

Patrick Sletvold

Content Security Policy Manager is a WordPress plugin that allows you to easily configure <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" rel="nofollow ugc">Content Security Policy headers</a> for your site. You can have different CSP headers for the admin interface, the frontend for logged in users, and the frontend for regular visitors. The CSP directives can be individually enabled, and each policy can be set to enforce, report or be disabled.
Please note that this plugin offers limited help in figuring out what the contents of the policy should be. It only lets you configure the CSP in a easy to use interface.

Content Security Policy Manager

Plugin for configuring Content Security Policy headers for your site. Allows different CSP headers for admin, logged inn frontend and regular visitors

MJP Security Tools vs Content Security Policy Manager