by Webmasters.Team 0 (0 reviews)

WT Hardening

Name: WT Hardening
Author: Webmasters.Team

WordPress hardening without touching your theme: XML-RPC, user enumeration, login limiter, security headers, strong passwords, event log.

WT Hardening ranks #26,700 among WordPress.org plugins with 20+ active installations, is #1,582 of 5,058 in the Security category, and was last updated Sep 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.0.7 Current Version v1.0.7

Updated 1 month ago Last Update on 21 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#1,582 of 5,058 in Security Top 50% by installs

View on WordPress.org

Rank

#26,700

— No change

Active Installs

20+

— No change

KW Avg Position

0.5 worse

Downloads

653

+4 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 30

Total Progress 80%

20+ 30+

3,955

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 2 more installs to reach 30+

Rank Changes

Current #26,700

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.7
Last Updated: Sep 21, 2026
Requires WP: 6.0+
Tested Up To: 7.1.4
PHP Version: 8.0 or higher
Author: Webmasters.Team

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

Brute Force hardening security Security Headers xmlrpc

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about WT Hardening

No. Everything is wired through WordPress hooks. Deactivating the plugin instantly reverts all changes (except HSTS, which browsers cache - enabling HSTS is a conscious decision).

Possibly, if you actually rely on them. Disable the XML-RPC module in the settings - the other protection layers stay active.

The table stays in the database (useful for later analysis). On full uninstall the tables are dropped cleanly.

Tested on a single-site install. Multisite should work since we do not use superadmin-specific APIs, but it is not yet formally supported - file an issue if something breaks.

Modules only register the hooks they actually need. The event log is a single INSERT per event. No scanner, no background work beyond an hourly and daily cleanup of old rows. Real impact on response time: under 1 ms.

Because Strict-Transport-Security has a sticky effect - browsers remember the header for a year. Enabling it too early (before your entire traffic works on HTTPS without errors) can lock users out of the site for a long time. Turn it on once HTTPS is rock-solid.

No - the policy hooks into admin form validation (profile, registration, reset). Programmatic user creation bypasses these hooks by design. For a typical client workflow (users are created through the admin panel) this is enough.