# Fix WordPress security findings in bulk, and undo them

Tick findings, press Apply Fix, and read the list before BetterShield changes anything. What the one-press fixes do, which wait for you, and how Undo works.

By M Asif Rahman, Nov 13, 2026. Updated Nov 19, 2026.

To fix WordPress security findings in bulk with **BetterShield**, open **BetterShield › Findings**, tick the rows you want, press **Apply Fix (n)**, read the list in the confirmation and press **Apply n Fixes**. Each finding is fixed exactly as its own **Apply Fix** button would fix it, and you can undo the whole set afterwards.

The idea is simple, but a button that changes a live site deserves a clear explanation. This guide says what one press changes, which fixes are included, which findings still ask you a question first and how to take a fix back. If you want the wider picture of what the audit checks, start with [what the security audit looks at](/blog/wordpress-security-audit/); this post covers what you do with the results.

## Quick summary

- **Apply Fix** on a finding applies the correction that finding offers and records the change. It does not apply every possible correction.
- Tick several rows and **Apply Fix (n)** counts the ones that have a one-press fix. Rows whose fix asks you something first are left out.
- BetterShield 1.1.5 added one-press fixes, each with **Undo**, for file permissions, folders anyone can write to, plugin updates, inactive plugins and themes, and dormant accounts.
- If one fix cannot change its item, the others still run, and the receipt lists what was applied and what was skipped.
- Fixes are in the free plugin, and not every change on a site can be reversed by a plugin, so read the confirmation first.

## Why a fix button needs care

A finding tells you the truth about your site. A fix changes the site, so the two deserve different amounts of attention. Reading a finding is free and changes nothing. Pressing a fix writes to your site, which is why BetterShield records every change and why every protection here is meant to be undone.

That is also why bulk is not the same as blind. The confirmation shows the list of fixes before anything runs, and the **Apply Fix** wording is the same one you would see on a single row. If you are new to the screen, read [Score and findings](/docs/score-and-findings/) first, and [the evidence behind a finding](/docs/finding-details/) for why a result matters before you act on it.

## What Apply Fix does

**Apply Fix** applies the correction offered for that finding and records the change. Some fixes switch on a protection. Others change file permissions, update a plugin or suspend an account. The same press can mean quite different things depending on the finding, so the finding’s own text and **Explain** panel tell you what this one does.

Three findings had a fix of their own before 1.1.5, each with **Undo**:

- Common usernames, with **Refuse These Names**.
- Proof of work, with **Turn On Sign-in Puzzle**.
- Pingbacks, with **Block Pingbacks Only**.

BetterShield’s own automatic updates have one too: **Apply Fix** switches them on in one press.

## The five fixes added in 1.1.5

BetterShield 1.1.5 added direct fixes, each with **Undo**, for five more findings. They can run from their row or as part of a bulk selection.

| Finding | What the fix does | What the way back is |
|---|---|---|
| File permissions | Stops other accounts on the server from writing to wp-config.php | **Undo** puts the earlier permissions back |
| Folders anyone can write to | Stops other accounts on the server from changing the listed folders; your site keeps working | **Undo** returns each folder to its earlier permissions |
| Plugin updates | Updates the plugin through WordPress’s own installer, as **Update now** under Plugins does | **Undo** puts the earlier code back, not the database changes |
| Inactive plugins and themes | Moves a deactivated plugin or an unused theme to quarantine, where nobody can run it | **Put back** returns it, settings and all |
| Dormant accounts | Suspends an unused admin-level account | Letting the account back in restores it; nothing is deleted |

Some of these deserve a closer look.

**Permissions.** On a Windows server permissions are not set this way, so BetterShield says it cannot change them and suggests asking your host to stop other accounts writing to these files.

**Plugin updates.** An update can change a plugin’s database tables as well as its files, and **Undo** only restores the code. Make a backup first. BetterShield says so if it sees no active backup plugin, and suggests checking that your host keeps one.

**Quarantine.** A quarantined plugin or theme leaves the site’s folders and is kept as a copy no one can run. Its uninstall step does not run, so its settings stay. You can put it back from the quarantine list or from the **Activity** screen. Our guide to [file quarantine](/docs/file-quarantine/) explains the list.

**Dormant accounts.** The list names accounts that look unused, and you untick anyone who is only away. A suspended account keeps its role, content and passwords, and cannot sign in by password, passkey or application password until you let it back in.

## Set it up

1. Open **BetterShield › Findings** and keep the **Open** tab selected.
2. Press **Explain** on a finding and read **What to know first** for anything that could affect your site.
3. Press **Apply Fix** on a single finding, or tick several rows to start a bulk selection.
4. For a bulk selection, press **Apply Fix (n)**. The number counts the rows that have a one-press fix. Rows whose fix asks you something first are left out, so you answer those on their own.
5. Read the list of fixes in the confirmation, then press **Apply n Fixes**.
6. Read the receipt. It lists what was applied and what was skipped, and one fix that cannot change its item does not stop the rest.
7. Check the finding. It updates on its own and your score changes. If it stays open, press **Check Again**, which says what the check still sees.

## What a bulk press does not do

It does not apply every correction you could make by hand, and it does not skip the questions that matter. A fix that needs a decision, such as one that changes how people sign in, is not counted in **Apply Fix (n)**. You answer it on its own row.

It also does not make every change reversible. The fix’s own **Undo** is there for the ones that can be undone, and a plugin update’s undo depends on the earlier package still being available. Some actions outside BetterShield cannot be reversed by the plugin, and the confirmation says so where it applies.

## What it can break, and how to undo

Each fix has a different risk, so the list is short and specific:

- **File permissions and folders.** A tighter permission can stop a tool or host script that wrote to those paths. Press **Undo** to restore the earlier permissions, then ask your host or the tool’s author which account should own the file.
- **Plugin updates.** New code can break a site in ways putting the old version back does not fully reverse, which is why a backup matters.
- **Quarantine.** A site that relied on an inactive plugin’s code, or on an unused theme as a fallback, can notice it is gone. **Put back** restores it. For a routine that keeps plugins and themes tidy month by month, see [WordPress plugin and theme hygiene](/blog/wordpress-plugin-theme-hygiene/).
- **Suspended accounts.** Someone who was only away cannot sign in until you let them back in. Tell them first, and untick them in the list.

After a bulk press you can undo the whole applied set at once, or undo a single fix from its own row. A protection switch can also be found under **BetterShield › Protection**, where the matching protection shows as on. If you want a deeper look at the protections and their undo, the post on [WordPress hardening](/blog/wordpress-hardening/) walks through them. And if a change ever leaves you unable to sign in, [set up recovery](/docs/set-up-recovery/) before you start, and keep our guide to [getting back in](/blog/locked-out-of-wordpress/) to hand.

## Snooze or mark not applicable instead

Not every finding should be fixed today. If a result is real but must wait, **Snooze** offers **In 7 days** and **In 30 days**. The finding stays open and still affects the score. If you have checked that another plugin, your host or your own process handles a job, **I Manage This Myself** (in BetterShield 1.1.7 or newer) moves the finding to **Not applicable**. That is your declaration; BetterShield does not verify the protection for you. Neither action changes WordPress, and **Unsnooze** or **Move back to Open** reverses them. The [manage findings guide](/docs/manage-findings/) covers both.

## Check it is working

1. After a fix, open the finding. It should move to **Fixed** without you running an audit.
2. If it does not, press **Check Again** and read what it still sees.
3. Confirm the score changed. [How the score and grade work](/docs/security-score/) explains the points.
4. Test the part of the site the fix touched: sign in, load a page, check the plugin you updated.
5. Look in the activity log, where each change is recorded with its own Undo.

## Recommended settings

We recommend working with a current backup and a working recovery method, and applying one kind of fix at a time on a site you cannot afford to break. Bulk is the right tool for a clean-up you have already read: ten permission changes and a handful of unused plugins, say, not a mixed list of everything open. The WordPress developer handbook’s [hardening guide](https://developer.wordpress.org/advanced-administration/security/hardening/) explains why permissions and unused code are worth tightening, and it is a good second opinion on the reasons behind these findings.

## Frequently asked questions

### Does Apply Fix change every finding?

No. Only findings that offer a fix show **Apply Fix**. Other rows link to the WordPress or BetterShield screen that handles them, and the link opens the setting itself.

### Can I undo a bulk fix?

Yes, for the fixes that have an **Undo**. Each is applied as its own **Apply Fix** would be, and you can undo the applied set afterwards. A plugin update’s undo restores the earlier code but not database changes.

### What happens if one fix fails?

The others still run. Read the receipt, which lists both applied and skipped items, and press **Check Again** on the one that stayed open.

### Are these fixes in the free plugin?

Yes. BetterShield is free on WordPress.org, and the fixes described here are in the free plugin from 1.1.5.

### Is it safe to apply fixes without a backup?

We recommend a current backup before you change anything on a live site, and always before a plugin update. Permission, quarantine and account fixes each have an Undo, but a backup covers what a plugin cannot reverse.

## Conclusion

Fixing findings in bulk is a way to spend a few minutes on a clean-up you have already read, not a way to stop reading. Tick the rows, read the list, apply the set and check the result, knowing each fix has its own way back. BetterShield is free on [WordPress.org](https://wordpress.org/plugins/bettershield/), and the full steps are in the [Apply a fix from a finding](/docs/apply-finding-fixes/) guide.
