BetterShield
Appearance
Security auditHardeningSettings

WordPress plugin and theme hygiene: updates and abandoned code

· · 11 min read

WordPress plugin and theme hygiene means three habits: install the updates that are waiting, remove what you no longer use, and replace code that nobody maintains any more. BetterShield turns each habit into a finding on BetterShield › Findings, says what to do about it, and for the common cases offers Apply Fix with Undo.

None of this is exciting, and that is the point. A site rarely gets into trouble because of one clever problem. It gets there because old code sat in a folder for two years. This guide goes through the findings that cover plugins and themes, what each one costs your score, and what can go wrong when you act on it. If you want the wider picture of what the audit looks at, read what a 57-check scan looks at first. To fix several findings at once, see fix WordPress security findings in bulk, and undo them.

Quick summary

  • Plugin updates are one finding, Plugins have updates available, which covers every pending update and costs 2 points of site health.
  • Deactivated plugins or themes are still installed is a Low finding. Its fix moves the ones you will not use again into quarantine, and Put Back restores them with their settings.
  • Plugins and themes that WordPress.org removed, or has not updated for years, have findings of their own. BetterShield names them, and you decide whether to replace them.
  • Apply Fix with Undo covers plugin updates and inactive plugins and themes. Take a backup you can restore before you update anything.
  • None of these findings is a malware verdict. They describe how well-kept your code is, not whether it is safe.

Why tidy code matters

Every plugin and theme on a site is code that runs, or can be reached, whether or not you remember installing it. Updates are how fixes for known problems reach you. Files left behind by a deactivated plugin can still be opened from the web, and they often miss updates, which is the reason BetterShield gives for its inactive-items finding.

There is also an upkeep side. The WordPress documentation on managing plugins describes how to install, activate, deactivate and delete them. BetterShield does not replace any of that. It tells you which of those jobs is waiting for you, so the list is short and specific.

The findings, and what each one costs

Your score has two parts: 60 points for setup essentials and 40 for site health. Each open finding in the table below takes points from site health, by severity: 2 for Medium and 1 for Low. How the score is worked out has the full rules.

FindingCostsWhat to do
Plugins have updates available2 · MediumUpdate the plugins listed in Fix and test what they do. One finding covers every pending update.
Deactivated plugins or themes are still installed1 · LowMove the ones you do not use to quarantine from Fix. Keep the active theme and its parent theme.
An installed plugin is no longer in the WordPress.org directory2 · MediumFind out why it was closed, then replace or remove it.
An installed plugin has had no WordPress.org update for years1 · LowAsk the developer whether it is still maintained. Replace it if it is abandoned.
There are files in your plugins folder that don’t belong to any plugin1 · LowCheck the named files with your developer or host before you touch them.

Themes follow the same pattern. In release 1.1.8, An installed theme is no longer in the WordPress.org directory and An installed theme has had no WordPress.org update for years name themes the directory removed or stopped updating, the same way the plugin findings do.

Keep plugins and themes updated

Updates come first because they are the habit that pays most often. When one or more plugins have a newer version, the single finding Plugins have updates available lists them in Fix.

Set it up

  1. Open BetterShield › Findings and select Details beside Plugins have updates available. Read What to know first.
  2. Take a backup you can restore, including the database.
  3. Select Apply Fix, or tick the row with others and use Apply Fix (n). Complete any confirmation shown, and read the result.
  4. Test the parts of the site those plugins run, such as checkout, forms or the front page.
  5. Press Check Again if the finding stays open. It says what the check still sees.

Since release 1.1.5, plugin updates are among the findings that can be fixed in one press, from the row or in bulk, each with Undo. Apply a fix from a finding covers the screen in full.

A note on Undo for updates: it depends on the earlier package still being available. Putting an old version back does not always reverse every kind of breakage either, because new code may already have changed the database. That is why the backup is step 2, not an afterthought.

What BetterShield Ultra adds

BetterShield Ultra has an optional policy, Fix vulnerable plugins automatically, that updates eligible plugins with known security issues under rules you choose. It starts off. It needs Ultra 1.0.9 or newer, the free BetterShield plugin active, vulnerability checks turned on and a current advisory result. Its first setting, Act on vulnerabilities rated, starts on Critical only. An eligible update also needs an available publisher update, host write access and a usable rollback copy. Update vulnerable plugins automatically has the steps. This is a premium feature for those who want it. The free findings above work without it.

Remove what you no longer use

A deactivated plugin is not gone. It is still in the plugins folder, and its files can still be opened from the web. The finding Deactivated plugins or themes are still installed asks you to decide, item by item, whether you will use it again.

Set it up

  1. Open the finding and read the list in Fix.
  2. Leave out the active theme and its parent theme. Those are in use even when they look idle.
  3. Move the items you will not use again to quarantine.
  4. Check the site, then come back in a week. If something was needed after all, Put Back restores it.

Quarantine is a better first step than deleting. The finding’s own guidance is that Fix moves those you will not use again into quarantine, with Put Back, and keeps their settings, while deleting one can remove its settings. A copy kept aside is described in Review files kept in quarantine.

If the finding There are files in your plugins folder that don’t belong to any plugin appears, the advice is the opposite of tidying up in a hurry. Check the named files with your developer or host. Quarantine suspicious files and remove confirmed leftovers. Leave a file alone until you know what it is.

Replace abandoned code

Some code is not broken, just left alone. BetterShield reads two signals from WordPress.org: that a plugin or theme is no longer in the directory, and that it has had no update there for years. Neither says why. The directory does not explain a removal, and some small plugins are simply finished.

SignalWhat it meansWhat to do
No longer in the WordPress.org directoryIt will get no more updates from WordPress.orgFind out why it was closed. Before you rely on an update, confirm it fixes the reason.
No WordPress.org update for yearsIf nobody maintains it, a flaw found in it may never be fixedCheck its page and the author’s site first, since a newer release may be elsewhere. Replace it if it is abandoned.

For a theme, the same rule holds, with one extra warning: switching the active theme changes how the site looks, so try a replacement on a copy of the site first. We recommend treating the Low finding as a prompt to ask a question, and the Medium one as a reason to plan a replacement.

Files can tell you something too

BetterShield’s file checks help with the other half of the question, whether the code on disk is the code that was published. Plugins from WordPress.org and supported WPDeveloper paid plugins are compared with the published checksums for their exact version. Plugins without published checksums are watched against their earlier state instead, and WordPress.org does not publish theme checksums, so the active theme and its parent are watched the same way. A watched copy is not a verified match to an official release.

Since 1.1.8, an added PHP file that decodes code and runs it, or hides behind a name starting with a dot, is marked worth a look, with the line shown. That is a signal, not a malware verdict. Read the code and its origin before you restore, quarantine or accept anything. Check files against their published copies and Put an official file back cover both screens.

What it can break, and how to undo

  • An update can break a plugin that depends on the old behavior. Use Undo on the row if the earlier package is still available, and restore your backup if it is not.
  • Moving an inactive plugin to quarantine can break a site that relied on it quietly, such as a theme that still calls it. Put Back restores it with its settings.
  • Removing a plugin that the directory closed can remove a feature the site needs. Find the replacement first, on a copy if you can.
  • Switching a theme changes how the site looks. Do not do it on the live site as an experiment.

Every one of these is a change to code your site runs, so the order is the same each time: backup, one change, test, then the next.

Check it is working

After a fix, the finding and your score update on their own. The finding should move to Fixed when the check passes. If it does not, press Check Again. Done recently shows one undo line for the fix you just made, and a link to more when there are more. On Activity, the related entry has Put Back.

We recommend a short monthly pass: open Findings, clear Plugins have updates available, quarantine anything you have not used for months, and read the abandoned-code findings as questions for the developer. Apply one correction at a time on a site with a current backup and a working recovery method. The WordPress security checklist puts the habit in the context of the rest of a site’s upkeep.

Frequently asked questions

Should I delete inactive WordPress plugins?

Quarantine the ones you will not use again, rather than deleting them straight away. BetterShield’s Fix keeps their settings and gives you Put Back, while deleting can remove the settings. Delete later, once the site has run well without them.

Is a plugin with no recent update unsafe?

Not necessarily. Some small plugins are finished. BetterShield treats it as a Low finding because, if nobody maintains a plugin, a flaw found in it may never be fixed. Ask the developer whether it is maintained and replace it if it is abandoned.

What if a plugin is no longer in the WordPress.org directory?

Find out why it was closed. WordPress.org does not say. It is a Medium finding, costing 2 points, and the advice is to replace or remove the plugin. Before you rely on a later update, confirm that it fixes the reason the plugin was closed.

Do these findings mean my site has malware?

No. They are about how well-kept your code is. BetterShield has no malware scanner and does not clean sites. The file checks flag differences and unexpected files for you to review, which is a signal and not a verdict.

Does BetterShield update themes as well as plugins?

The update finding and the one-press fix cover plugin updates. For themes, BetterShield names the ones that were removed from the directory or have had no update for years, and it can quarantine inactive themes. Replace an abandoned theme on a copy of the site first.

Conclusion

Plugin and theme hygiene is small, regular work: update what is waiting, quarantine what you do not use, and ask questions about code nobody maintains. Back up first, change one thing at a time, and keep Undo and Put Back in reach.

BetterShield is free on WordPress.org. The doc for the fixes in this guide is Apply a fix from a finding.

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