zackdesign

AliasIO

<p>MJP Security Tools is a focused hardening plugin that does four things well:</p>
<ul>
<li><strong>XSS Database Scanner</strong> — scans every table for <code><script></code>, <code><iframe></code>, <code>onclick</code>, <code>javascript:</code> and other injection patterns</li>
<li><strong>POST Request Log</strong> — records all POST data (passwords masked) with IP, user agent, and URL for CSRF/audit detection</li>
<li><strong>Failed Login Log</strong> — tracks every failed login attempt with username, IP, and timestamp</li>
<li><strong>File Permission Checker</strong> — verifies WordPress root files and directories have safe permissions, checks for missing <code>index.html</code> files and SVN working copies</li>
</ul>
<p><strong>What this plugin does NOT do</strong> (because WordPress core already handles it):</p>
<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>
<p><strong>Upgrading from v1.x:</strong></p>
<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.

te_taipo

<h4>PARETO SECURITY FEATURES</h4>
<p>Had enough of the security theatre presented by the raft of WordPress security plugins? Time to put a stop to the attacks!</p>
<p>Firstly WordPress and most other CMS\’s are built using PHP. PHP is a very insecure programming language, even worse in the hands of amateurs.</p>
<p>WordPress has been plagued by plugins authored by amateurs that bring with them security vulnerabilities.</p>
<p>Security plugin designers mostly focus on cleaning up attacks rather than stopping them dead in their tracks.</p>
<p>Pareto Security class acts as a Central Security Hub checking all inputs from users, preventing bad requests from executing on your website.</p>
<ul>
<li>Real Attack Prevention that can be achieved via a plugin</li>
<li>Automatic Blacklist Management</li>
<li>Easy-To-Use</li>
<li>No customisation needed</li>
<li>Works silently, you only get notified when you really want to be notified</li>
<li>Completely Free</li>
<li>and much more…</li>
</ul>
<h4>PARETO SECURITY PROTECTION</h4>
<ul>
<li>Pareto Security Protection identifies and blocks malicious traffic.</li>
<li>Pareto Security Protection dynamic IP Blacklist protects your site while reducing load.</li>
<li>Protects your site at the entry-point, disabling attack peneration of your WordPress site.</li>
<li>Extends WordPress inbuilt security, defends your website against vulnerabilities added in via bad plugin coding.</li>
<li>[disabled] Optionally prevent Tor users/bots from interacting with login forms and search functions of your site while still allowing them to <em>view</em> your site.</li>
<li>Optionally only allow standard web clients and trusted crawlers to access your website, discouraging others from doing so.</li>
</ul>
<h4>PARETO SECURITY TOOLS</h4>
<ul>
<li>Monitor blocked attack attempts</li>
<li>Optionally receive notifications of <em>REAL</em> attack attempts that Pareto Security has blocked</li>
</ul>
<h4>A Word on Security:</h4>
<p>By the very nature of plugins, no plugin should ever claim to be a Web Application Firewall.</p>
<p>No security plugin can save your website from really-really badly written site, theme and/or plugin code.</p>
<p>No security plugin can save your site from attacks that result from when administrators do not follow basic security practices.</p>
<p>Keeping any CMS as secure as possible is not easy. The very best thing you can do to prevent attacks is to always keep your website code, themes and plugins up to date, and remove any plugins and themes you are not using.</p>


Pareto Security

WordPress Core Security: Secure your website with real security.

MJP Security Tools vs Pareto Security