# WordPress security checks explained: what each one covers

Which BetterShield check answers which question: the audit, the file check and vulnerability data, what each one sees, and what none of them is.

By M Asif Rahman, Nov 20, 2026.

WordPress security checks are not one thing: **BetterShield** runs three kinds, and each answers a different question. The audit asks how the site is set up, the file check asks whether the code on disk is the code that was published, and the vulnerability check asks whether an installed version has a published advisory.

If you want the number the audit produces, [WordPress security score: what it measures and what it cannot tell you](/blog/wordpress-security-score-explained/) covers it. This post is the map: which check to look at for which worry, and what none of them claims to do.

## Quick summary

- The **audit** reads settings and exposure: who can sign in, what a visitor can see, what is out of date, how the server and `wp-config.php` are set. It is read-only and runs once a day.
- The **file check** compares core, directory plugin and watched files with the copies WordPress.org publishes or with their own earlier state, and lists every difference.
- The **vulnerability check** is optional and off by default. With consent it matches installed versions against published advisories.
- A check that could not run, a file it could not compare or data that is old is never reported as clean.
- BetterShield has no firewall, does not scan for or remove malware, and a passing check is not a statement that nothing is wrong.

## Why it matters

A security screen can look like one big scanner, and that invites a wrong conclusion: a green grade must mean the site is clean. It does not, because each check only answers its own question. A site can pass every setting and still have a changed file, and it can match every published file and still run a plugin version with a known advisory.

Knowing which check covers what tells you where to look next. It also tells you what to read as a limit, not a result. BetterShield is built to say so: skipped checks are counted separately, stale data carries its age, and an unavailable result is shown as unavailable.

## Which check answers which question

| Your question | The check | Where to look |
|---|---|---|
| Is the site set up sensibly? | The audit | **BetterShield › Findings** |
| Can a visitor see or reach something they should not? | The audit | **BetterShield › Findings** |
| Is a core or plugin file different from what was published? | The file check | **BetterShield › Activity › File Changes** |
| Did a new PHP file appear that nobody released? | The file check | **BetterShield › Activity › File Changes** |
| Does an installed version have a published advisory? | The vulnerability check | **BetterShield › Findings** |
| Is the advisory data current? | The vulnerability check | The source and age of the result |

## The audit: how the site is set up

The audit compares the site with a list of known good settings and known weak spots. Each answer is a check, and a check that fails becomes a finding. The checks fall into five areas, the same five **BetterShield › Findings** uses: access, exposure, updates and extensions, server, and configuration.

Examples are idle Admin accounts, user profiles that visitors can list, missing security headers, the dashboard file editor, an outdated PHP version and secret keys in `wp-config.php` that are missing or unchanged. Since 1.1.10 a finding can also say that the server’s PHP is missing a security fix a newer release of the same version already has, and name the release to ask your host for.

The audit runs when the plugin is activated and once a day after that, and you can start one yourself. It reads; it changes nothing. [WordPress security audit: what 75 checks look at, and what they miss](/blog/wordpress-security-audit/) lists the areas in full, and the site’s [checklist](/checklist/) has every check.

The audit does not look inside files for hidden code, and it does not read the code of your plugins. That is the file check’s job, and only up to a point.

## The file check: whether the code is the code that was published

A checksum is a short fingerprint of a file’s contents. WordPress.org publishes checksums for supported core releases and many directory plugin versions, and BetterShield compares the files on your server with them.

| What | Compared with |
|---|---|
| WordPress core and directory plugins | The checksums WordPress.org publishes |
| Your active theme, must-use plugins, `wp-config.php` and plugins outside the directory | What each file was at the last check |

Core and directory plugins are checked every hour, in the background. Watched files are checked once a day. **Check now** starts one yourself. Supported WPDeveloper paid plugins are compared against checksums published by the publisher, and when no list exists for a version, that copy was not compared, which is different from matching. From 1.1.10 the active theme and its parent are also compared once with the copy WordPress.org published, when it lists them at your version.

Each difference names its file and what changed, and **Show the difference** opens the lines. **Put the official file back** restores the published copy for core and directory plugins and keeps yours in quarantine. Since 1.1.8 an added PHP file that decodes code and runs it, or hides behind a name beginning with a dot, is marked worth a look, with the line. That is a signal, not a verdict: read the code and where it came from before you restore, quarantine or mark it expected.

What the file check does not do is judge a file. A file that matches the published copy is not proved safe, only unchanged, and a watched file that matches its earlier state is not a verified match to an official release. [WordPress file integrity check: compare with the official copies](/blog/wordpress-file-integrity-check/) goes through the report in detail.

## Vulnerability data: whether a version has a published advisory

This check is optional and off by default. Open **BetterShield › Settings › General**, find **Check plugins, themes and WordPress for known security issues** and turn it on after reading what leaves the site: the names and versions of components, not the site address, an email or a key. The matching of versions happens on your site, and no Hub account or paid license is needed.

A result names the affected components and any available fix. Since 1.1.8 an advisory can also say whether it can be reached on this site, for example whether it needs no account or needs a role someone on the site holds. That helps you order the work. It does not hide the advisory and does not call the component safe.

The limits matter most here. While the check is off, the Findings screen says nothing was checked, and that is not the same as nothing being vulnerable. If a refresh fails, BetterShield keeps the last good result and shows a warning with its age. An unknown version or severity is not evidence of safety. [How to check for known vulnerabilities](/docs/vulnerability-checks/) has the details.

## What none of the three does

BetterShield is not a firewall, and it does not scan for or remove malware. It does not hold a database of malware signatures, it does not give a “clean” verdict, and it does not clean a site up. Its checks find what is wrong with settings, files and versions, and report it plainly. If you suspect a site is already compromised, that calls for a professional cleanup, not a green grade.

## What it can break, and how to undo

The three checks are read-only. They break nothing and there is nothing to undo, apart from the optional vulnerability check, which you turn off in **BetterShield › Settings › General** to stop future requests. Results already recorded do not become proof of a current clean result.

The actions beside a result are different. **Put the official file back** replaces a file on the site, so read the difference first, and take a backup if the change might be deliberate. Marking a change **Expected** tells BetterShield to stop raising that one, and a later change is still reported. [Put an official file back](/docs/restore-official-files/) covers the restore and its undo.

## Check it is working

- On **BetterShield › Overview**, the score card shows how many checks ran, how many could not, and the time of the latest audit.
- On **BetterShield › Activity › File Changes**, the **Last check** time and progress show a completed comparison, and anything not compared is named with its reason.
- With vulnerability checks on, the result shows its source, its last successful refresh and its age. Treat an old or unavailable result as a limit.

## Recommended settings

We recommend leaving the daily audit and the file check as they are, and turning on vulnerability checks when the data exchange fits your site. Run **Check now** after an update, a migration, a deployment or unexpected behavior. Start with the audit’s Critical and High findings, then read the file report, and plan updates from any advisory. A vulnerability result does not replace a backup, and a file check does not replace reviewing what you installed. For the order of work, [WordPress plugin and theme hygiene: updates and abandoned code](/blog/wordpress-plugin-theme-hygiene/) shows what to do about the extensions themselves.

For the platform’s own guidance on the hardening this audit looks at, the WordPress project’s [hardening documentation](https://developer.wordpress.org/advanced-administration/security/hardening/) is the reference.

## Frequently asked questions

### Does a high security score mean my WordPress site is clean?

No. The score summarizes the audit’s findings, which are about settings and exposure. It does not look inside files for hidden code, and BetterShield does not scan for malware. A high score means the checks pass, and the [score and findings doc](/docs/score-and-findings/) explains how to read it.

### What does the file check see that the audit does not?

It sees the code itself. The audit reads settings, while the file check compares core, directory plugin and watched files with the published copies or their earlier state, and lists what differs. [How BetterShield’s file integrity checks work](/docs/file-integrity-checks/) describes each kind of difference.

### Is a missing or old vulnerability result the same as a clean one?

No. If vulnerability checks are off, nothing was checked. If a refresh failed, the last good result is kept with a warning, and an unknown version or severity is not treated as safe. Read the source and age on the result before you rely on it.

### Which checks send anything outside my site?

Out of the box, the file check contacts WordPress.org, and WPDeveloper’s checksum servers for its paid plugins. Vulnerability checks stay off until you turn them on. [What BetterShield contacts](/docs/what-bettershield-contacts/) lists every service and what each request carries.

### Do I need to run the checks myself?

Not usually. The audit runs daily, the file check runs hourly for core and directory plugins, and the vulnerability check refreshes daily once it is on. Run one yourself after a change you made outside BetterShield.

## Conclusion

The audit tells you how the site is set up, the file check tells you whether the code matches what was published, and the vulnerability check tells you whether a version has a published advisory. None of them is a malware scan or a firewall, and each says plainly when it could not look. BetterShield is free on [WordPress.org](https://wordpress.org/plugins/bettershield/), and [Understand your security score and grade](/docs/security-score/) is the next doc to read.
