How to Secure WordPress with WP Toolkit Security Hardening

WP Toolkit includes a set of one-click security measures that close the most common holes hackers use on WordPress sites. This guide shows how to secure WordPress with WP Toolkit security hardening in cPanel, which measures are safe to turn on, and how to undo one if it causes a problem.

Before you start: make a backup

Most security measures can be switched off again, but a few (such as changing the database table prefix or the admin username) can't be undone. Create a backup in WP Toolkit first so you can roll back if anything goes wrong. See the WordPress backup guide in the related links below.

How to open WP Toolkit security measures

  1. Log in to cPanel and go to Domains > WordPress Management (WP Toolkit).
  2. Find your site in the list. On its card, click Security. (If WP Toolkit has already found a problem, the card may show a warning such as Fix security or a vulnerability notice instead. Click that.)
  3. A list of security measures opens, each with an on/off switch and a short description.
  4. Turn on the measures you want. WP Toolkit applies each one right away.

WP Toolkit groups the measures by importance. The most important ones are already applied on sites installed with WP Toolkit. The rest are recommended but optional, because a few can affect some plugins.

Which security measures should you turn on?

For most sites, it's safe to turn on everything below. The table shows what to watch for.

MeasureWhat it doesWatch out for
Block access to wp-config.phpStops anyone viewing your database password file over the web.Nothing, turn it on.
Block directory browsingHides folder listings.Nothing.
Block access to sensitive files and .htaccessBlocks log, config and backup files from being downloaded.Rare plugin conflicts.
Disable PHP execution in cache and uploads folders, and in wp-includesStops uploaded malware from running.Badly written plugins that keep PHP in those folders.
Block access to xmlrpc.phpStops a common brute-force and spam target.Breaks Jetpack, the WordPress mobile app and remote publishing. Leave it off if you use them.
Turn off pingbacksStops your site being used in pingback attacks.Nothing for most sites.
Disable file editing in the WordPress dashboardRemoves the theme/plugin code editor, so a stolen admin login can't inject code.Edit files with File Manager instead.
Block author scansHides admin usernames from bots.Nothing.
Enable bot protectionBlocks known bad bots.Nothing for most sites.
Configure security keysGenerates new WordPress secret keys.Logs everyone out once. Can't be reverted.
Change default database table prefixRenames the wp_ tables.Can't be reverted; old plugins that assume wp_ may break. Back up first.
Change default administrator usernameReplaces an "admin" username.Can't be reverted. Note your new username.

The exact wording in WP Toolkit may differ slightly from the names above, but each measure has a description next to it.

Check for vulnerable plugins and themes

Hardening doesn't fix a plugin with a known security hole. WP Toolkit also checks your WordPress version, plugins and themes against a vulnerability database and flags anything at risk on the site card. When you see a vulnerability warning, click it to see what's affected and update or remove that plugin or theme. Keeping everything updated is the single most effective security step. Turn on auto-updates as described in the update guide below.

How to undo a security measure

If your site, a plugin, or the WordPress admin stops working right after you applied a measure:

  1. Go back to Domains > WordPress Management (WP Toolkit) and click Security on the site's card.
  2. Switch off the measure you turned on most recently.
  3. Reload your site. If it works, leave that one off.

Measures that can't be reverted (table prefix, admin username, security keys) need a restore from backup if they cause trouble.

More ways to protect WordPress

  • Use a strong, unique admin password and remove admin accounts nobody uses.
  • Delete plugins and themes you don't use -- even deactivated ones can be exploited.
  • Make sure the site loads over HTTPS.
  • The Instant Access Internet Services server firewall also blocks IP addresses after repeated failed logins, which slows down password-guessing attacks.

Common questions

Does hardening make my site slower?

No. The one exception is the admin script concatenation option, which may make the WordPress dashboard load very slightly slower. Visitors won't notice.

I turned on a measure and now Jetpack or the WordPress app won't connect

Switch off the xmlrpc.php block. Those services need it.

My site was already hacked. Will this clean it?

No. Hardening prevents attacks but doesn't remove malware. Restore a clean backup from before the hack, change all passwords, then apply hardening. Open a ticket if you need help.

Related guides

Still stuck? Open a support ticket and the Instant Access Internet Services team will help.

Ultrafast LiteSpeed hosting from InstantAccess.net: free SSL, free backups, cPanel included, no contracts. Check out our $10/month hosting.
  • wordpress security, wp toolkit security, harden wordpress, wordpress hardening cpanel, block xmlrpc wordpress, wordpress vulnerabilities, secure wordpress site
  • 0 Корисниците го најдоа ова како корисно
Дали Ви помогна овој одговор?

Понудени резултати

How to Create a WordPress Staging Site and Push It Live

A staging site is a private copy of your WordPress website where you can test new plugins, theme...

How to Install WordPress with WP Toolkit in cPanel

WP Toolkit lets you install WordPress on your hosting account in a couple of minutes, with no...

How to Log In to WordPress Admin from WP Toolkit

You don't need to remember your WordPress password to get into your site. WP Toolkit in cPanel...

How to Update WordPress, Plugins and Themes (and Turn On Auto-Updates)

Keeping WordPress up to date is the single best thing you can do to keep your site safe. This...

How to Move a WordPress Site from Another Host (WP Toolkit Import)

Moving a WordPress site from another host doesn't have to mean downtime or lost content. This...