BetterShield
Appearance
Security auditSettingsChecklist

WordPress security score: what it measures and what it cannot tell you

· · Updated · 11 min read

A WordPress security score is one number from 0 to 100 that sums up what a security audit found, and the BetterShield score is built from two parts: 60 points for setup essentials and 40 points for site health, with a grade from A to F. It measures how your site is configured, and it reads the same way every time, so you can see exactly where each missing point went.

If you want the audit behind the number first, what a 76-check WordPress security audit looks at covers it. This post stays with the score itself: how it is added up, what a finding costs, which actions change it and which only change the report.

Quick summary

  • The score is 60 points for setup essentials plus 40 points for site health, and the free plugin can reach 100.
  • The grade bands are A (90 to 100), B (75 to 89), C (60 to 74), D (45 to 59) and F (below 45).
  • While any Critical finding is open, the score stops at 74, however high the sum is.
  • Snoozing a finding changes nothing about its cost. Marking a finding Not applicable removes it from the score, and that changes the report, not the site.
  • A high score means the audit’s checks pass. It is not a statement that nothing can go wrong, and BetterShield is not a firewall or a malware scanner.

Why it matters

A list of findings is accurate but flat. Forty items in a row do not tell you which to do first, and a site owner without time needs an order of work. The score is that order: it puts a price on every open finding, so the expensive ones rise to the top.

It also keeps the report honest. The number is calm, never red and never a countdown, and the Findings screen shows how it was reached, for example Setup 52/60 · Site health 35/40. You can check the sum yourself instead of trusting a badge. The note that a score is a reading aid, not a certificate, is part of the same idea: the audit reports what it can see.

How the score is worked out

The two parts behave differently, so it helps to keep them apart.

PartPointsWhat lowers it
Setup essentials60The points of each setup item that is still open
Site health40A deduction for every other open finding, by severity; never below zero

There are 16 setup items, checked by 17 findings. Examples are requiring two-factor for privileged roles (10 points), limiting sign-in attempts (8) and confirming your recovery options (6). A setup finding costs its own points and nothing more. The dashboard file editor is enabled costs 5 setup points even though its severity is Medium, and it does not also take 2 health points.

Every other open finding takes points from site health by severity:

SeverityPoints removed while open
Critical10
High5
Medium2
Low1
Info0

Some findings change severity with the situation. An expiring certificate, for instance, costs more as the days run out. The finding on your own screen always shows its current cost under Effect on the score.

The cap at 74

While a Critical finding is open, the total stops at 74. The cap is a ceiling, not an extra deduction. A site with 60 setup points and 30 health points adds up to 90, but shows 74 until its Critical finding is fixed. A score that is already below 74 stays where it is. The Findings screen adds Held at 74 while a critical finding is open when the cap applies, so you are never left guessing why a number did not move.

Worked examples

Open findingsCalculationScore
None60 + 40100, A
Sign-in limits off, nothing else(60 − 8) + 4092, A
One Critical finding: private files can be downloaded60 + (40 − 10) = 90, held at 7474, C
All setup done, health findings adding up to 4660 + 0, because health stops at zero60, C

The last row explains a common surprise. Fixing a 5-point health finding there leaves 41 points of deductions, so the score stays at 60. The fix still counts: the next 2-point fix takes the deductions to 39 and the score to 61. In the same way, while a Critical finding holds the score at 74, other fixes may not move the number until that one is closed. The security score guide lists what every finding costs.

What moves the score, and what only changes the report

Closing a finding moves the score. Changing how a finding is shown does not always, so it is worth knowing which is which.

  • Fixed: a passing check closes its finding and gives back its points. Undoing the change can open it again.
  • Snoozed: Snooze hides the finding for 7 or 30 days. It stays open, still costs its points and still triggers the cap if it is Critical.
  • Not applicable: takes the finding out of the score. Move back to Open brings it back.
  • I manage this myself: puts supported findings in Not applicable and keeps your choice after new scans. The score shows how many items you marked. It records your decision. It does not prove the protection works.
  • Could not check: never counts as a pass. A finding that was already open keeps its cost until a fresh result is available.
  • A protection with no finding: adds no points on its own. The score follows the list of checks, not the number of switches you turn on.

Snoozing a finding or marking it not applicable walks through each action. We recommend using Snooze only for a time-bound reason, and Not applicable only when you have confirmed the check really does not apply to this site, not because the fix is inconvenient.

Raise the score, step by step

There is no scoring setting to change. You raise the score by closing findings.

  1. Open BetterShield › Findings and start with the Critical and High results.
  2. Open a finding and read Why it matters, Evidence and What to know first. Effect on the score shows what that one finding costs.
  3. Use the action it offers: Apply Fix, Fix, Open Hardening or How to Fix. Read any confirmation, then test the part of the site the change affects.
  4. Before you change anything about signing in, make sure your way back in works. Set up recovery comes first.
  5. Press Check Again if you want to confirm. The finding should move to Fixed, and the score and the setup and health breakdown update to match.

A fix made in BetterShield updates the score on its own. A change made somewhere else, such as WordPress itself, your host or a file manager, shows up the next time you open a BetterShield screen once the last audit is five minutes old, or at the next scheduled audit. Run Audit brings it in at once. Apply a fix from a finding explains the details, and fixing several findings at once, and undoing them covers the faster route.

What it can break, and how to undo

Calculating the score only reads your site and changes nothing. The fixes behind it are what change the site, and each one has its own undo, so follow its guide before you apply it. The snooze and not-applicable actions change reporting only, and Unsnooze or Move back to Open reverses them.

One thing can look like a problem and is not. If you updated from a version before 1.1.3, your score may jump after the update without anything new going wrong on the site, because earlier versions took 25, 12, 7 and 3 points for Critical, High, Medium and Low from a single 100. Grade boundaries did not change. If a script uses wp bettershield audit --fail-under, check its threshold against the current numbers. WordPress security from the command line lists the commands.

What the score cannot tell you

A score is a summary of checks, and a summary has edges. Say them out loud and the number becomes more useful.

  • It does not mean the site is clean. BetterShield has no malware scanner and no signature database, and a high score means the audit’s checks pass.
  • It does not cover what the audit cannot see. A check that could not run stays listed as such and never counts as a pass.
  • It does not compare your site with anyone else’s. The number says where your own points went.
  • It does not decide for you. Read it with the evidence and with any notice about checks that could not run.

BetterShield Ultra is not needed to reach 100. No part of the score is kept for paid features.

For wider habits, what to look at in WordPress security each week turns the score into a routine, and the WordPress developer handbook on hardening WordPress is a good outside reference for the settings behind many of the findings.

Check it is working

To see the score without opening BetterShield, the Dashboard widget shows it on Dashboard › Home.

  1. Open BetterShield › Findings and read the line under the score. It should show Setup and Site health as two numbers that add up to the total.
  2. Fix one finding, then compare the finding and the breakdown. Both should update.
  3. If the number did not move, look for Held at 74 while a critical finding is open, or for a health total already at zero.
  4. Open a finding’s Effect on the score to see exactly what it costs.

We recommend this order:

  1. Fix every Critical finding first. Nothing else can lift the score past 74 while one is open.
  2. Confirm your way back in, then require two-factor for privileged roles and turn on sign-in limits. Together they are worth 24 setup points.
  3. Apply the one-click hardening items in the setup table: the file editor, usernames, browser protections, folder contents and the WordPress version.
  4. Work through High findings, then Medium, then Low.

Read the evidence before you apply a fix, and check the change works for the people who use the site. Compare audit results by day shows whether the score is trending the way you expect.

Frequently asked questions

Why is my score low if nothing looks wrong?

Setup findings cost their own points even when the site seems fine, because the score counts protections that are not switched on yet. Open the finding’s Effect on the score to see what each one costs. A snoozed finding still counts, and a finding marked Not applicable does not.

Why did my score not change after I fixed something?

Either a Critical finding is holding the total at 74, or the site health part is already at zero, so one fix does not show until the deductions fall far enough. Press Check Again, then look for the Held at 74 line.

What is a good score?

A is 90 to 100 and B is 75 to 89, but the number is for your own use. It is an order of work for this site, not a measure against other sites. A Critical finding holds even a perfect sum at 74.

Can I reach 100 with the free plugin?

Yes. BetterShield Ultra is not needed, and no part of the score is kept for paid features.

Does marking a finding Not applicable fix it?

No. It takes the finding out of the score and records your decision. The site does not change, so use it only when the check truly does not apply.

Conclusion

The score adds up 60 setup points and 40 health points, stops at 74 while a Critical finding is open and shows its working on the Findings screen. Use it as an order of work, read the evidence before you act, and remember that it describes how the site is set up, not whether it is clean.

BetterShield is free on WordPress.org. The docs cover each part: Security score, Score and findings and Run and monitor scheduled audits.

Close the open doors today

Install the free plugin. The first audit runs when you activate it, and all but one of the fixes wait for your choice.

Requires WordPress 6.7 or newer and PHP 8.0 or newer.

Get BetterShield