Security Hardener

Security Hardener has one disclosed vulnerability in the WordSec catalog, all reported in 2026; it is fixed as of August 2026. Their average CVSS score is 8.8, and the most serious one scores 8.8 out of 10. Severity breakdown: 0 critical and 1 high.

The most common weakness is Improper Privilege Management, behind 1 of the records (100%).

The one issue recorded for Security Hardener has a vendor fix available, so running the current release closes it.

All of these findings were reported by zickzick2. Security Hardener is installed on roughly 200 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.1.

Strategic Overview

Avg CVSSHigh
8.8/ 10
Patch Coverage100%
Open

0

Fixed

1

Get automatic notifications for all Security Hardener vulnerabilities before they are exploited.

Highest severity on recordCVSS 8.8CVE-2026-16149

Security Hardener <= 2.4.4 - Authenticated (Subscriber+) Privilege Escalation via REST API '/wp/v2/users' permission_callback Overwrite

Read the full analysis

Vulnerability Records

1 records
Plugin Profile
Latestv2.4.5

Security Hardener

Marc Armengou

Author

Marc Armengou

0.0(0)
0/100
Last Updated
2026-08-19 (4d ago)
Active Installs
200+
Downloads
2,020
Requires WP
6.9+
Requires PHP
8.2+
Tested up to
WP 7.1
Created
2025-11-03 (10mo ago)

Security Hardener applies WordPress security best practices based on the WordPress Advanced Administration / Security / Hardening documentation and widely accepted hardening measures. It uses WordPress core functions and follows best practices without modifying core files. Key Features 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 /?author=N 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 (/author/username/feed/) * 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: * X-Frame-Options: SAMEORIGIN (clickjacking protection) * X-Content-Type-Options: nosniff (MIME sniffing protection) * Referrer-Policy: strict-origin-when-cross-origin * Permissions-Policy (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 ⚠️ Important: Always test security settings in a staging environment first. Some features may affect third-party integrations or plugins. 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.

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C