Find out which sites are at risk, then fix the easy stuff.

Each WordPress site gets Security, found under Tools in its menu. It lists known vulnerabilities in WordPress and in the plugins the site runs, plus a short list of risky settings you can fix with a click.

For WordPress sites. Needs the KontrolWP Connect plugin.

Known problems, ranked by how bad they are.

KontrolWP compares each site's WordPress and plugin versions with the Wordfence Intelligence vulnerability feed and flags any match.

  • Every issue gets a CVSS score, from Low to Critical
  • You also see the CVE, a link to the full report and the version that fixes it
  • Settings show a checkmark when fine, Fix now when KontrolWP can do it for you, and a warning when you need to change it yourself
  • Fix all in the header takes care of every open item at once

The details

How it works, point by point.

Vulnerabilities

  • Each issue shows its CVSS score and level, such as 6.4 (Medium). Colors run from yellow for Low up to dark red for Critical
  • Under the rating you can see whether a fixed version exists
  • KontrolWP checks WordPress and every plugin on the site, using the versions from the last sync
  • Themes are not checked, because a site only reports the name of its active theme

Where the data comes from

  • The data comes from the Wordfence Intelligence feed. You add a free API key from a Wordfence account once, on the Integrations page, and it is stored encrypted
  • KontrolWP downloads the feed once a day, and again when you save the key. There is no refresh button because Wordfence allows only one download every 30 minutes
  • If a download fails, KontrolWP keeps what it already has and shows a quiet note
  • This checks a public vulnerability feed and a few settings. It does not scan files for malware

Settings you can fix

  • One list shows what is fine, what you can fix now and what needs a manual change, with open items first
  • It looks at HTTPS, an out-of-date PHP version, a pending core update, inactive plugins and a user named admin (that one you change yourself)
  • Fix now applies the fix and turns into a checkmark. Fix all applies every open one
  • The fixes: no directory listing, hide the WordPress version, remove RSD and Windows Live Writer links, hide database and PHP errors, delete readme.html, and turn off the code editor and XML-RPC
  • Checkmarks come from the live site, so they also count protection that something else provides

Custom login address

  • Move the WordPress login form to an address you choose, like WPS Hide Login does. Set it in the Login page section of a site's Security view under Tools
  • Signed-out visitors who go to wp-login.php or wp-admin get a 404 page, or a redirect to the home page if you prefer
  • Password reset emails, logout and Magic Login links are updated to use the new address
  • Easy to undo: switch it off, clear the address, deactivate the plugin, or add one line to wp-config.php, and wp-login.php works again
  • Admin AJAX, REST, XML-RPC, cron and WP-CLI are never touched. It stays off while WPS Hide Login or a similar plugin is active

Per site

  • You can turn security checks off for a single site in its settings. Scheduled work skips it, Security is hidden from Tools, and anything already stored is kept

Take control of every WordPress site you run.

Deploy KontrolWP to your Cloudflare account and connect your first site.