Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Guide

How to Scan with Wordfence (Step by Step)

How to Scan with Wordfence (Step by Step)

Short answer

Open Wordfence in your dashboard, go to Scan and click Start New Scan. When it finishes, review the results by severity, repair modified official files, delete confirmed malware, update vulnerable plugins, and run a second scan to confirm everything is clean.

Key takeaways

  • Start a manual scan from Wordfence, then Scan, then Start New Scan.
  • Standard scan suits most sites; high sensitivity suits suspected hacks.
  • Back up before repairing or deleting any flagged file.
  • Premium plugins may need a fresh reinstall instead of repair.
  • Ignore results only after you have checked them.
  • Failed scans usually need more memory or execution time.

How do you run a scan with Wordfence?

Go to Wordfence > Scan in your WordPress dashboard and click Start New Scan, then wait for each stage to finish and review the results list that appears below the progress bar.

A full scan checks your core files, themes and plugins against known good copies. It also looks for malware signatures, known vulnerabilities, weak passwords and suspicious content. The Wordfence plugin page summarises these features.

Scans run in the background on your server. You can leave the page and come back, although the first scan on a large site can take a while.

If Wordfence is not installed yet, follow our guide on installing the Wordfence plugin first, then come back to this page.

What does a Wordfence scan check?

A Wordfence scan compares your WordPress files with official copies, searches files and content for malware patterns, flags plugins and themes with known vulnerabilities, and checks for weak admin passwords and risky settings.

The scan runs in stages, and the progress bar shows each one as it finishes. The exact list depends on your version and licence.

Scan areaWhat it looks for
Core, theme and plugin filesFiles changed from the official repository versions
Malware signaturesKnown malicious code patterns in files
ContentSuspicious links or code in posts and comments
Public filesBackup or log files that anyone could download
VulnerabilitiesInstalled plugins and themes with known security flaws
Users and passwordsWeak passwords on admin accounts
Server stateDisk space and similar warnings

Free sites get the same scanner as paid sites, but new malware signatures reach free users later. Wordfence lists the differences on its plans page.

How do you start a manual scan step by step?

Open the Scan page, click the start button, and keep the page open until the progress indicator shows that every stage has completed.

  1. Log in to WordPress as an administrator.
  2. Go to Wordfence > Scan in the left menu.
  3. Click Start New Scan.
  4. Watch the stage indicators move from left to right.
  5. When the scan finishes, scroll down to the results list.
  6. Open each result to see the file or setting involved and the suggested action.

You can click the scan log link to watch detailed progress. That log is helpful if a scan stalls or fails.

If the button is greyed out, a scan may already be running. Wait a few minutes, or use the stop option if a scan has hung.

Which scan type should you choose?

Most sites should keep the standard scan, use high sensitivity when you suspect a hack, and use the limited scan only on hosting that struggles with resource use.

You change this under Wordfence > Scan > Scan Options and Scheduling. Wordfence documents each setting on its Scan Options help page.

  • Limited scan checks fewer areas and uses fewer server resources. It suits small shared hosting plans with strict limits.
  • Standard scan is the recommended default and covers the main checks.
  • High sensitivity scans more file types and areas. It can produce more false positives but is useful during a cleanup.
  • Custom scan lets you choose individual checks yourself.

High sensitivity is a good choice for a one-off scan after a suspected attack. Switch back to standard afterwards so daily scans stay light.

If scans push your server too hard, our guide to Wordfence high CPU usage explains how to reduce the load.

How do you read the scan results?

Each result shows a severity level, a short description, and buttons to view details, repair, delete or ignore the issue, so start with critical items and work down.

Results are grouped by severity. Critical items need attention first. Medium and low items are often warnings rather than active problems.

Common results include:

  • Modified core or plugin file. A file differs from the official version.
  • Unknown file in WordPress core directories. A file that is not part of WordPress sits next to core files.
  • Plugin needs an update. A newer version is available, sometimes with a security fix.
  • Plugin has a known vulnerability. Update or replace it as soon as possible.
  • Publicly accessible config or backup file. Remove or protect it.

Use View details or the file view to see the change before acting. Some changes are legitimate, such as edits made by your host.

How do you fix the issues a scan finds?

Use Repair to restore a modified core, theme or plugin file from the official copy, Delete for files that should not exist, and update plugins with known vulnerabilities.

Always make a full backup before repairing or deleting files. A backup lets you undo a mistake. Our guide on how to back up a WordPress site covers the options.

A safe order of work is:

  1. Update WordPress core, themes and plugins.
  2. Repair modified files that come from WordPress.org.
  3. Review unknown files and delete clear malware.
  4. Change passwords for any account flagged as weak.
  5. Run a new scan to confirm the issues are gone.

Premium themes and plugins cannot always be repaired automatically, because Wordfence has no official copy to compare with. Reinstall them from the vendor's download instead.

If the scan finds malware in many places, follow a full cleanup process such as our guide on how to clean a hacked WordPress site.

When should you ignore a scan result?

Ignore a result only when you have checked it and are sure it is safe, such as a file your developer changed on purpose or a known false positive in a premium plugin.

Wordfence offers two ignore options. One ignores the result until the file changes again. The other ignores it permanently.

The first option is safer. If the file changes later, Wordfence will warn you again.

Do not ignore results just to clear the list. A modified file you do not recognise is worth a closer look.

How do you schedule automatic scans?

Wordfence schedules scans automatically, and on paid licences you can set your own days and times under Scan Options and Scheduling.

Free sites have scans scheduled for them on a regular cycle. Paid licences can choose a custom schedule, which is useful for running scans during quiet hours.

Wordfence explains the details on its scan scheduling help page.

Make sure WordPress scheduled tasks run correctly, because scheduled scans rely on WP-Cron. The WordPress cron documentation explains how WP-Cron is triggered by site visits.

How do you get email alerts about scan results?

Set your alert email and choose which issues trigger an email under Wordfence > All Options > Email Alert Preferences.

Alerts are useful because they tell you about problems even when you do not log in. You can choose to receive alerts only for critical issues to cut down noise.

If alerts never arrive, the problem is usually WordPress email delivery, not Wordfence. An SMTP plugin fixes most cases, as explained in our guide to setting up SMTP in WordPress.

What should you do if a scan fails or stalls?

If a scan stops part way, check the scan log for the last stage, then raise PHP memory and time limits or switch to a lighter scan type.

Common causes include low PHP memory, short maximum execution times, very large files, and hosts that block loopback requests.

Wordfence keeps a list of fixes on its scan troubleshooting page. It covers settings such as the maximum execution time and how many files to scan per stage.

Raising memory often helps. The PHP manual explains the memory_limit setting that controls it. Our guide to increasing the PHP memory limit shows where to change it.

You can also exclude large folders that do not hold code, such as cache or backup folders, from the scan.

Can you scan a site without logging in to WordPress?

Yes, Wordfence offers a command line scanner that can scan files on the server without using the WordPress dashboard, which is useful when the site is down.

This is handy if malware has locked you out or the site shows a fatal error. It needs SSH access to the server.

See our guide on how to use Wordfence CLI for setup and example commands.

For a quick outside check you can also use an online scanner, but those only see public pages. A server-side scan finds far more.

Frequently asked questions

How long does a Wordfence scan take?

A small site often finishes in a few minutes, while large sites with many plugins and uploads can take much longer. Scan time depends on the number of files, the scan type and your server speed. High sensitivity scans take the longest.

Is the free Wordfence scan good enough?

The free scanner uses the same engine as the paid version and finds most common problems. The main difference is that new malware signatures and firewall rules reach free sites after a delay, and paid licences add extra checks and custom scheduling.

Will a Wordfence scan slow down my website?

A scan uses server resources while it runs, which can slow busy sites on small hosting plans. If you notice slowdowns, use the limited scan type, reduce the number of files scanned per batch, or schedule scans for quiet hours where your licence allows it.

Does Wordfence remove malware automatically?

No. Wordfence shows the problem and offers repair or delete buttons, but you choose what to do with each result. Always back up first and check that a file is truly malicious before you delete it.

Why does Wordfence flag files from my premium theme?

Wordfence compares files with official copies on WordPress.org. Premium themes and plugins are not hosted there, so harmless code can sometimes match a malware pattern. Check the file, compare it with a fresh vendor download, and ignore it only once you are sure.

Sources

  1. Wordfence Scan Options Wordfence
  2. Wordfence Scan Scheduling Wordfence
  3. Wordfence Scan Troubleshooting Wordfence
  4. Wordfence Security WordPress.org Plugin Directory
  5. Cron WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.