Why WordPress.org Closes Plugins: 52,534 Closures From 2004 to 2026

52,534 plugins are currently closed on WordPress.org, and the most common reason is a guideline violation (30.3%). The fastest-growing reason is security: closures for security issues went from about 100 a year before 2021 to 1,985 in 2024.
Share this: WordPress.org has closed 52,534 plugins. Security closures rose from about 100 a year to 1,985 in 2024. (PluginCanary, November 2026)
The six reasons plugins get closed
| Reason | Share of closed plugins | What it usually means |
|---|---|---|
| Guideline violation | 30.3% | The plugin broke a directory rule, such as tracking users without consent, locking features in the free version, or spam |
| Unused | 22.5% | Approved but never used or updated; often closed in bulk sweeps |
| Author request | 17.1% | The developer asked WordPress.org to close it |
| Not stated | 13.3% | No reason recorded, mostly older closures |
| Security issue | 12.3% | An unpatched vulnerability, or malicious code |
| Licensing or trademark | 4.4% | GPL licensing problems or a trademark complaint |
Security closures are climbing

Security closures stayed between 100 and 160 a year from 2018 to 2020, then jumped to 561 in 2021 and peaked at 1,985 in 2024. 2025 added 1,646 more. A security closure does not remove the plugin from sites that already run it, so each one leaves sites exposed until owners act.
Share this: WordPress.org closed 1,985 plugins for security issues in 2024, nearly 20 times the 2020 figure. (PluginCanary, November 2026)
The 2018 purge

In 2018 WordPress.org closed 14,276 plugins, more than any other year. 9,750 of them were closed as unused, 9,076 of those between May and August, in a cleanup of plugins that had been approved but never used. Another 3,279 were closed for guideline violations that year.
Authors walk away too
Every year since 2018, developers have asked WordPress.org to close between 823 and 1,155 of their own plugins. Licensing and trademark closures spiked to 1,054 in 2025, from 7 the year before.
Mass closures
Sometimes WordPress.org closes several plugins from one author at once. Since January 2025 we have recorded 173 such events covering 889 plugins: 87 events (384 plugins) in 2025 and 86 events (505 plugins) so far in 2026. The largest was EssentialPlugin, with 33 plugins closed on 7 April 2026 after a backdoor was found.
What to do when a plugin you use is closed
- Find out why. The plugin page on WordPress.org shows a closure notice; the date and reason matter.
- If it was closed for security, act now. Check whether a patched version exists. If not, deactivate and replace it.
- If it was closed for another reason, it will receive no more updates from WordPress.org. Plan a replacement before the next major WordPress or WooCommerce update.
- Test the replacement on a staging copy, move your settings, then remove the old plugin.
See the WooBeWoo plugins for actively maintained WooCommerce extensions.
How we counted
Data from PluginCanary, snapshot 16 November 2026; closures by year are from the 10 November 2026 snapshot. Counts include only plugins that are still closed: WordPress.org drops the closure record when a plugin reopens. Closure reasons are reliably recorded from 2017 onward; most earlier closures have no stated reason.