Marc Armengou

Security Hardener applies WordPress security best practices based on the <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" rel="nofollow ugc">WordPress Advanced Administration / Security / Hardening</a> documentation and widely accepted hardening measures. It uses WordPress core functions and follows best practices without modifying core files.
<h4>Key Features</h4>
File Security: 
* Disable file editor in WordPress admin 
* Optionally disable all file modifications
XML-RPC Protection: 
* Disable XML-RPC completely 
* Remove pingback methods when XML-RPC is enabled
Pingback Protection: 
* Disable self-pingbacks 
* Remove X-Pingback header 
* Block incoming pingbacks
User Enumeration Protection: 
* Block <code>/?author=N</code> queries (returns 404) 
* Secure REST API user endpoints (require authentication) 
* Remove users from XML sitemaps 
* Prevent canonical redirects that expose usernames 
* Optionally block author feed pages (<code>/author/username/feed/</code>) 
* Optionally anonymize the author name in oEmbed responses
Login Security: 
* Generic error messages (no username/password hints) 
* Login honeypot 
* Block unsafe usernames 
* Application Passwords disabled by default 
* IP-based rate limiting with configurable thresholds 
* Security event logging
Security Headers: 
* <code>X-Frame-Options: SAMEORIGIN</code> (clickjacking protection) 
* <code>X-Content-Type-Options: nosniff</code> (MIME sniffing protection) 
* <code>Referrer-Policy: strict-origin-when-cross-origin</code> 
* <code>Permissions-Policy</code> (restricts geolocation, microphone, camera) 
* Optional HSTS (HTTP Strict Transport Security) for HTTPS sites — max-age set to 1 year
Additional Hardening: 
* Hide WordPress version (meta generator tag and asset query strings) 
* Remove obsolete wp_head items (RSD, WLW manifest, shortlink, emoji scripts) 
* System Status — monitors file permissions, WP_DEBUG, user registration, PHP version, administrator accounts, and database version
<blockquote>
⚠️ Important: Always test security settings in a staging environment first. Some features may affect third-party integrations or plugins.
</blockquote>
Privacy: This plugin does not send data to external services and does not create custom database tables. It stores plugin settings and a security event log in the WordPress options table, and uses transients for temporary login attempt tracking. All data is preserved on uninstall by default and only deleted if the “Delete all data on uninstall” option is explicitly enabled.

Security Hardener

Basic hardening: secure headers, login honeypot, user enumeration blocking, generic login errors, rate limiting, and more.

Kashif Ahmed Khan

VigiGuard Security provides essential WordPress protection without complexity. One-click hardening, brute force protection, and file integrity monitoring – all with zero configuration required.
Key Features:
<ul>
<li>One-Click Fix – Secure your site instantly with one button</li>
<li>Brute Force Protection – Blocks repeated login attempts automatically </li>
<li>Security Health Score – Visual A-F grade showing your security status</li>
<li>File Integrity Monitor – Scans 3,000+ WordPress core files weekly</li>
<li>Activity Logging – Track all security events and login attempts</li>
<li>Security Hardening – Disables XML-RPC, hides WP version, blocks user enumeration</li>
</ul>
Perfect For:
<ul>
<li>Small business owners who need security without the hassle</li>
<li>Bloggers who want “set and forget” protection</li>
<li>Freelancers managing multiple client sites</li>
<li>Anyone who finds other security plugins too complicated</li>
</ul>

VigiGuard Security

Simple one-click WordPress security. Protect your site in 30 seconds.

Security Hardener vs VigiGuard Security