ismycodesafe.com
WordPress Security Scanner

Free WordPress Security Scanner

Scan your WordPress site for outdated core, exposed admin pages, leftover backup files, weak SSL, and 150+ other security issues. Get results in 60 seconds.

Scan My WordPress Site. Free

No signup · No credit card · Scan runs in 60 seconds, verify your email to view results

Rather not remember to rescan? We can scan your site every month and email you the results. See pricing

What the scanner checks

Plugin risk

Patchstack's 2025 data puts 91% of new WordPress vulnerabilities in plugins and only 6 in core. A remote scan cannot list your plugin versions, so we check the JavaScript libraries your plugins load against known CVEs and point you to the checklist below for the rest.

Exposed wp-admin and wp-login

Finds /wp-admin and /wp-login.php when they are publicly reachable and looks for signs of rate limiting or MFA on the login page.

Outdated WordPress core

Identifies running an outdated WordPress version and maps it to known CVEs.

Leftover files

Requests wp-config.php.bak, .old and .save copies, .sql dumps in the webroot, /wp-includes/version.php and the /wp-json/ index.

Missing security headers

WordPress does not set CSP, X-Frame-Options, or HSTS by default. We find which are missing.

Weak cookie flags

Checks the Secure, HttpOnly and SameSite flags on every cookie the site sets to a visitor.

Why WordPress Security Matters

WordPress runs 39.6% of all websites (W3Techs, October 2026). Its weak spot is the plugin ecosystem: Patchstack's 2025 data puts 91% of new WordPress vulnerabilities in plugins, 9% in themes and only 6 in core. The fix is almost always the same: update or remove outdated plugins with known CVEs.

Our scanner combines CVE lookup against the NVD and OSV databases, real-time SSL analysis with SSLyze, and OWASP Top 10 checks. On WordPress it looks for the misconfigurations it can see from outside: leftover wp-config.php backups, missing security headers, cookies without Secure or HttpOnly, and a public /wp-json/ index.

WordPress security checklist

The scan covers what is visible from outside. This list covers the rest, in the order we would work through it on a site we just inherited.

  1. Run wp plugin list --fields=name,status,version,update and update everything that has an update. Delete plugins that are inactive everywhere, they still sit on disk and can still be reached.
  2. Put MFA on every administrator account and remove admins nobody can name.
  3. Add define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php. It removes the theme and plugin editor from wp-admin, so a stolen admin password cannot be turned into PHP on the server in two clicks.
  4. If nothing uses XML-RPC (the Jetpack app and some old clients do), block /xmlrpc.php at the web server.
  5. Keep backups off the server. A backup in the webroot is a .sql file waiting to be downloaded, which is one of the paths the scan above requests.
  6. Run the free scan again after each change and check that the finding is gone.

Running WordPress Multisite?

A Multisite network is one WordPress install serving many sites from one database and one plugin folder. That shared core is why the security questions differ from a single site, and why most of them can only be answered from inside the network.

The free scan tests one URL at a time from the outside. On a Multisite network that means one subsite per scan. It reads that site's TLS certificate and security headers, and requests known leftover paths such as /wp-config.php.bak, /wp-config.php.old, /wp-includes/version.php and /wp-json/. Run it once for the main site and once for every subsite on its own domain, because a mapped domain can sit behind a different certificate or CDN rule than the network root.

It cannot see network admin settings, who holds super admin, or whether one subsite's admin can reach another subsite's data. For that you need shell access and WP-CLI:

# every site in the network, including archived and deleted ones
wp site list --fields=blog_id,url,archived,deleted,spam

# who can change the whole network
wp super-admin list

# plugins forced on for every subsite
wp plugin list --status=active-network

# plugins inactive on the main site (they may still run on a subsite)
wp plugin list --status=inactive --fields=name,version,update

That last list is not a delete list. On Multisite a plugin can be inactive on the main site and active on one subsite. Before you remove anything, check each site:

wp site list --field=url | while read -r site; do
  echo "== $site"; wp plugin list --url="$site" --status=active --field=name
done

A plugin that shows up nowhere in that output, and not in the active-network list above, is unused on the whole network. Update it or delete it.

Two results deserve attention. A long super admin list is the first thing to shrink, because a super admin can install plugins that run on every site in the network. And archived or deleted sites with a custom domain often leave a DNS record pointing at a host nobody controls any more. Check each mapped domain:

dig +short CNAME shop.example.com

If the target is a service you no longer use (an old hosting account, a deleted storage bucket, an expired SaaS page), remove the record. A dangling CNAME is how subdomain takeovers start.

Frequently Asked Questions

Can I check my WordPress site for vulnerabilities online for free?

Yes. Enter your URL above and the scan runs from the outside in about 60 seconds, with no signup or card. It reads the WordPress core version, exposed files, headers and TLS, and checks the JavaScript libraries your pages load. Plugin versions are not visible from outside, so pair it with wp plugin list --fields=name,version,update on the server.

How do I check if my WordPress site is secure?

Run an automated scan for core version, security headers, SSL/TLS and exposed files, then list your plugins on the server with wp plugin list and update the ones that have updates. Our free scanner does the outside part in 60 seconds and emails you a full report with fix instructions.

What are the most common WordPress security issues?

Vulnerable plugins (91% of new WordPress vulnerabilities in 2025, per Patchstack), outdated core, weak admin passwords, exposed xmlrpc.php, missing security headers, and leftover .sql backups in the webroot.

Is the WordPress scanner really free?

Yes. The full scan is free with no signup or credit card required. Once the scan completes we send you a verification email - click the link and your results plus the detailed email report unlock immediately. Premium AI-generated fix reports are available for $29.

Will the scan harm my WordPress site?

No. Most checks only read publicly available endpoints the same way Googlebot does. A few are light active probes: a check of common ports, an anonymous FTP login attempt, and one request carrying a SQL-injection pattern to test for a web application firewall. We never exploit a finding, brute-force logins, or test authenticated areas.

Does the scanner detect malware on WordPress?

The scanner checks if your site is listed on Google Safe Browsing, PhishTank, URLhaus, and Spamhaus DBL blocklists. For a quick outside malware check, run Sucuri SiteCheck. Our comparison page explains what it can and cannot see. For files on the server, use a plugin such as Wordfence.

Ready to scan your WordPress site?

Free, no signup. Verify your email to view the detailed report with fix instructions.

Run Free WordPress Scan

Free Security Tools

Run individual checks on your WordPress site for free.

Other Stack Scanners

Running more than WordPress? These scanners check stack-specific issues the generic scan does not look for.

Expert Help

Book a security review for your WordPress site

30-minute consultation with a security engineer. Covers your scan results, how to fix critical issues, and what to prioritize. Free, no sales pitch.

Book Free Consultation

Claude AI helped me with phrasing and proofreading in this article.