Backups & maintenance · Guide
How to Spot an Abandoned WordPress Plugin
Short answer
To spot an abandoned WordPress plugin, open its WordPress.org page and check the last updated date, the tested-up-to version, and any closure notice. Treat a plugin as abandoned if it has no update in over 2 years, shows the untested warning, or has been closed. Replace it with a maintained plugin after a backup, and test the site before you delete the old one.
Key takeaways
- Wordfence defines an abandoned plugin as one with no update in over 2 years.
- A closure notice on WordPress.org means the plugin can no longer be downloaded or updated there.
- The untested warning appears when a plugin was last tested 3 or more major WordPress releases ago.
- In 2025, 91% of new WordPress vulnerabilities were in plugins, so unmaintained code is the main risk.
- Back up your site before you replace a plugin, and keep the old one deactivated for a few days first.
- Premium plugins need the same check on the vendor site, since the directory cannot flag them.
What counts as an abandoned WordPress plugin?
An abandoned plugin is one its author no longer updates or supports.
No single date proves it. Judge a plugin by several signs together: its last update date, its tested-up-to version, and any closure notice on its WordPress.org page.
The scale of the problem is large. A scan of the full directory on 18 November 2026 counted 76,461 plugins, and 44,392 of them, or 58%, had an update in the last 2 years, according to WP.MD.
| Signal | Where to see it | What it means |
|---|---|---|
| Last updated | Plugin page sidebar | Date of the latest release |
| Tested up to | Plugin page sidebar | Newest WordPress version the author checked |
| Closure notice | Top of the plugin page | The directory removed the plugin from downloads |
| Active installations | Plugin page sidebar | How many sites still run it |
Why does an abandoned plugin put your site at risk?
An abandoned plugin can carry a security hole that no one will ever fix.
Patchstack counted 11,334 new vulnerabilities across WordPress in 2025, up 42% on 2024, and 91% of them were in plugins, according to its State of WordPress Security in 2026 report.
The same Patchstack report found that 46% of those vulnerabilities had no fix from the developer by the time they were made public. For the most heavily attacked flaws, the weighted median time from disclosure to mass exploitation was 5 hours.
Wordfence found that about 35% of the vulnerabilities disclosed in 2024 were still unpatched in 2025. An old flaw in an abandoned plugin can stay open for years.
A security plugin can scan your installed plugins and flag ones that look abandoned or removed from the directory. Start with a scan from one of the security plugins, then work through the flags by hand.
What do you need before you start checking?
You need admin access to your site, a list of your plugins, and a backup made before you change anything.
- An administrator login for your WordPress dashboard.
- A backup of your files and database, made with one of the backup plugins.
- Your WordPress version, shown on the Dashboard → Updates screen.
- Your PHP version, shown under Tools → Site Health → Info → Server.
- About 30 minutes for a typical site with 10 to 20 plugins.
Do not skip the backup. You will deactivate and delete plugins later in this guide, and a backup is the only fast way back if a page breaks.
How do you check when a plugin was last updated?
Open the plugin's page on WordPress.org and read the “Last updated” date in the sidebar.
- In your dashboard, go to “Plugins” → “Installed Plugins” and note each plugin name.
- Click “View details” under a plugin name to open its info window.
- Read “Last updated” and “Tested up to” in that window.
- Open the same plugin's page on WordPress.org to see the full sidebar, including active installations.
- Write down the date and the tested version for each plugin, then sort by oldest first.
Use these bands as a starting point, not a verdict.
- Less than 12 months since the last update: no action from this sign alone.
- 12 to 24 months: look for a replacement and read the support forum for unanswered questions.
- Over 24 months: plan to replace it soon.
Wordfence defines an abandoned plugin as one that has not been updated in over 2 years. Its scanner flags such plugins, and it raises a critical alert when a plugin has been removed from WordPress.org but is still installed on your site.
Read the WPLegible review of Wordfence to see what its scanner checks on each run.
What does “hasn't been tested with the latest 3 major releases” mean?
It means the plugin's “Tested up to” version sits 3 or more major WordPress releases behind the current one.
The warning on the plugin page reads: "This plugin hasn't been tested with the latest 3 major releases of WordPress."
The warning comes from the “Tested up to” value, not from the last update date. A plugin updated last month can still show it if the author did not raise the tested version.
WordPress 7.1 was released on 19 August 2026, and the latest build is 7.1.4, a security release from 28 October 2026, according to Make WordPress Core. As of November 2026, a plugin tested only up to 6.8 or lower shows the warning.
WordPress 7.2 is scheduled for 8 December 2026, according to Make WordPress Core. After it ships, the warning will move up a version, so a plugin tested only up to 6.9 will show it.
Old code can also clash with new PHP versions. WordPress.org recommends PHP 8.3 or greater as of November 2026, and WordPress still runs on PHP 7.4 and later in legacy setups, though those versions are past end of life.
How do you tell if a plugin has been closed on WordPress.org?
A closed plugin's page shows a notice that it is not available for download, with the closure date.
Closure removes the plugin from search results and downloads, and sites that already have it get no more updates. The installed copy keeps working, but no fix will ever reach it through WordPress.org.
The directory shows the reason for the closure after 60 days. Reasons include Security Issue, Author Request, Guideline Violation, Licensing/Trademark Violation, Merged into Core, and Unused, according to the Detailed Plugin Guidelines.
A security closure needs fast action. The plugin guidelines say a plugin found to have security issues is closed until the problem is fixed, so check the reason and replace it at once.
Not every closure is permanent. Read the notice: some say the closure is permanent, and others leave the door open for the author to fix the problem and return.
How do you check plugins that are not in the WordPress.org directory?
Check the vendor's own site for a changelog, a recent release date, and a support page that still answers questions.
Premium plugins sit outside the directory, so there is no closure notice and no tested-up-to warning for them. The vendor's changelog and release history are your only signals.
- A new version or changelog entry in the last 12 months.
- Support replies from the vendor in the last few months.
- A vendor site that still lists the plugin for sale or download.
If you cannot find a release in the last 2 years, treat the plugin the same way you would treat an abandoned directory plugin. Plan a replacement before it breaks.
How do you pick a replacement plugin?
Pick a replacement that is updated often, tested with your WordPress version, and used by many sites.
Open the replacement's WordPress.org page and check the same signs you used above. A good replacement passes every one of them.
- Last updated within the last 6 months.
- “Tested up to” matches your WordPress version, which is 7.1 as of November 2026.
- Active installations in the thousands or more, so many sites rely on it.
- Recent replies from the author in the support forum.
- A changelog that lists bug fixes, not only new features.
Check that the replacement covers the features you actually use. Open your old plugin's settings first and note each feature, then match them one by one.
Check the replacement's “Requires WordPress version” and PHP requirement in its sidebar. WordPress.org recommends PHP 8.3 or greater as of November 2026, so a replacement that needs an older PHP version is a warning sign.
How do you replace an abandoned plugin safely?
Back up first, install the replacement, move your settings, then deactivate and delete the old plugin.
- Make a full backup of your site. Follow the WPLegible guide to back up WordPress before you touch any plugin.
- Install the replacement from the WordPress.org directory or the vendor's site, then set it up while the old plugin is still active.
- Copy your settings across: forms, shortcodes, widgets, and any page that used the old plugin.
- Deactivate the old plugin under “Plugins” → “Installed Plugins”, then test the pages that used it.
- Keep the old plugin deactivated for a few days. If nothing breaks, delete it from the same screen to remove its files.
- Clear your site cache if you use one, then check the front end once more.
The swap takes about 30 minutes for a simple plugin, and longer for one tied to many pages or a shop checkout. Work on a staging copy first if your host provides one.
How do you check that the replacement worked?
Visit the pages that used the old plugin and confirm each feature still works.
- Open every page that used the old plugin and check its layout.
- Submit its form, or run its main feature once, and confirm the result.
- Look for new error notices in your dashboard.
- Check that emails the plugin used to send still arrive.
If a page breaks, reactivate the old plugin and restore your backup. Then look for a different replacement or ask your host for help.
What mistakes should you avoid?
The biggest mistake is deleting a plugin before you have a working replacement and a backup.
- Deleting the old plugin before the replacement is tested.
- Judging a plugin by its last update date alone, without its tested version and support replies.
- Replacing a simple plugin that still works and has no known security problem only because it is old.
- Installing a replacement without checking its own update history first.
- Forgetting the pages, forms, and shortcodes that used the old plugin.
A shorter plugin list also makes your site easier to maintain. Fewer active plugins can help your pages load faster, as the WPLegible guide to speeding up WordPress explains.
How often should you repeat this check?
Check your plugins twice a year, and again before every major WordPress update.
WordPress 7.1 arrived on 19 August 2026, and 7.2 is scheduled for 8 December 2026, according to Make WordPress Core. A plugin that was current in August can be 2 releases behind by December, so check again after each major release.
Put the check on your calendar for June and December. A security plugin scan on the same dates catches plugins you missed by hand.
Frequently asked questions
Is it safe to keep using a plugin that still works but has no updates?
It can keep working for a long time, but no one will fix a new security hole in it. If the plugin handles logins, payments, forms, or uploads, replace it soon. If it is a simple plugin with no known flaw, you can keep it while you look for a replacement, and check it again at your next review.
Can I keep a plugin that WordPress.org has closed?
Your installed copy will keep running, but it will never get another update through WordPress.org. If the closure was for a security issue, stop using it right away. For other reasons, check the closure notice, keep a backup, and plan a replacement instead of leaving it in place for years.
What if no replacement plugin does the same job?
First check whether a different plugin covers the features you actually use, even if it works in another way. If nothing fits, ask the original author whether they plan to return, or look for a developer who can take over the plugin through the WordPress.org adoption process. Do not install a random fork without checking its own update history.
Should I delete an abandoned plugin or only deactivate it?
Deactivate it first and test your site, then delete it after a few days with no problems. Deactivating stops the code from running, while deleting also removes its files from your server. Keep a backup before you delete, so you can bring it back if a page you missed turns out to need it.
Does an abandoned plugin slow down my site?
Not by itself. A plugin only adds load on pages where its code runs, so a small abandoned plugin may have no visible effect on speed. The real cost is risk: old code can clash with a new WordPress or PHP version, and a flaw in it will never be fixed. Remove plugins you no longer use in any case.
How often should I check my plugins for abandonment?
Check twice a year, and again before every major WordPress update. WordPress ships major releases a few months apart, so a plugin that was current in August can be 2 releases behind by December. A short check after each major release catches new warnings before they turn into broken pages.
Sources
- Detailed Plugin Guidelines WordPress Developer Resources
- Plugin Developer FAQ WordPress Developer Resources
- Take Over an Existing Plugin WordPress Developer Resources
- Requirements WordPress.org
- State of WordPress Security in 2026 Patchstack
- How the Wordfence Scanner Protects Your Site Wordfence
- WordPress Plugin Statistics 2026 WP.MD
- Release Posts Make WordPress Core
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.
Thanks — we review requests within 3 business days.
