Skip to content
webfixed

Guides / WordPress

Host flagged a vulnerable WordPress plugin and the site went down

By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1.

Short answer

Some hosting panels scan WordPress plugins for known vulnerabilities and offer a delete button, which removes the plugin’s files outright. If other plugins, the theme or your pages relied on it, the site breaks. Restore it from a backup, or reinstall the same version from wordpress.org, then update it to the version that fixes the vulnerability.

Symptoms

You may see this message:

Some required plugins are missing or inactive.

  • The site went down, or lost its design, straight after you used a delete option on your hosting control panel’s security or vulnerability screen.
  • The plugin is no longer listed under Plugins, and its folder is gone from wp-content/plugins.
  • Pages show shortcodes as plain text in square brackets, or sections built with a page builder have gone.
  • The dashboard shows "Some required plugins are missing or inactive.", or says a plugin has been deactivated because "Plugin file does not exist."
  • The site shows "There has been a critical error on this website." or a blank page.

Causes, most likely first

  1. The delete option removes the plugin itself

    A vulnerability warning is about one version of a plugin. A delete option on a host’s scan screen can remove the plugin’s folder from the server rather than the warning, and it does this outside WordPress, so none of WordPress’s own checks run.

  2. Other plugins depended on it

    Add-ons for WooCommerce, page builders and form plugins need their main plugin. Without it they may stop working or crash the site.

  3. A caching plugin left a file behind

    When caching is on, WordPress loads a file called advanced-cache.php from wp-content early on every page. Caching plugins put it there. If the plugin is deleted and that file stays, it can call code that no longer exists.

  4. A parent theme was deleted

    Scans flag themes too. If your site uses a child theme and its parent is deleted, WordPress reports "The parent theme is missing." and the site loses its design.

  5. Content used the plugin’s shortcodes or blocks

    WordPress leaves shortcodes it does not recognise untouched, so they appear as text in square brackets. Content built with the plugin’s blocks or page builder loses those parts.

How to fix it

Put the plugin back

The quickest way back is to return the same plugin to the server. Its settings are normally still in the database, because deleting the files from the server does not run the clean-up a plugin can do when it is deleted from inside WordPress.

  1. Check your host’s backups for one taken shortly before the delete. If the host lets you restore single folders, restore wp-content/plugins followed by the plugin’s folder name.
  2. A full restore also works, but it rolls the database back too, so orders, form entries and edits made since that backup are lost.
  3. If there is no usable backup, open the plugin’s page on wordpress.org and click Advanced View. Under Previous Versions, choose the version you had, which the host’s warning usually names, and click Download.
  4. For a paid plugin, download the same version from your account on the developer’s site.
  5. Click Upload Plugin, choose the zip file and click Install Now.Menu: Plugins > Add Plugin
  6. Check the plugin is active. If nobody opened the Plugins screen while it was missing, it is still marked active and comes straight back. Otherwise WordPress will have deactivated it, so click Activate.Menu: Plugins > Installed Plugins

wordpress.org warns that previous versions of plugins may not be secure or stable. Reinstall the old version only to get the site back, then update it straight away.

If a caching plugin or theme was deleted

  1. Reinstalling a deleted caching plugin normally brings the site back, because its advanced-cache.php file has its code again.
  2. If you do not want the caching plugin back, download a copy of wp-content/advanced-cache.php, delete it from the server, and change define( 'WP_CACHE', true ); to false in wp-config.php.
  3. For a deleted theme, click Add Theme, then Upload Theme, choose the theme’s zip file and click Install Now. For a child theme, the parent theme is the one to reinstall.Menu: Appearance > Themes

Then deal with the vulnerability properly

  1. Look the plugin up in a vulnerability database. WPScan lists a Fixed in version for each record, and Patchstack and Wordfence Intelligence show which versions are affected.
  2. Compare that with the version you have. If a fixed version exists, that is the version to move to.
  3. If the site takes payments or leans heavily on the plugin, and your host offers a staging copy, test the update there first.
  4. Update the plugin to the fixed version or later.Menu: Dashboard > Updates
  5. If there is no fixed version, deactivate the plugin rather than delete it, check every page and form still works, then replace it with a maintained alternative.
  6. Delete plugins from the Plugins screen in WordPress, not from the hosting panel. WordPress then applies its own checks first.

Treat a host’s warning as real until you have checked it. In the case described further down, the warnings were genuine.

If that didn’t work

  1. The plugin is back but parts of the site are still broken

    Clear every cache, including the host’s and any content delivery network’s, then check again. If an add-on still fails, the PHP error log names it.

  2. Settings are missing after reinstalling

    If the plugin was deleted from inside WordPress rather than from the server, it may have removed its settings from the database. Restoring the database from a backup taken before the delete brings them back.

  3. More than one plugin or theme was deleted

    Compare the plugins and themes folders with a backup to find everything that went, including drop-in files such as advanced-cache.php in wp-content.

What hosting vulnerability scanners do

Several hosting control panels include a WordPress tool that compares the plugins and themes on your site with a database of known vulnerabilities. When it finds a match, it shows a warning and may offer actions such as updating, deactivating or deleting. Some can install security updates automatically. Updating and deactivating leave the plugin on the server. Deleting from the hosting panel removes it, and it does not go through WordPress’s own checks first.

How Plugin Dependencies affects this

Since WordPress 6.5, a plugin can name the plugins it needs in a Requires Plugins header. WordPress then will not let you delete a required plugin while plugins that need it are installed, or deactivate it while they are active.

That protection only works inside WordPress. When a required plugin is deleted from the server, by a hosting panel, FTP or a deployment, WordPress shows "Some required plugins are missing or inactive." and marks the affected plugins, but it still loads them. Whether they fail safely depends on how each one was written. The feature also only covers plugins that declare what they need, and does not cover themes that need plugins.

A case we dealt with

On one site we look after, the host’s vulnerability scan flagged the theme and a caching plugin, with a Delete button beside each. Pressing it deleted the theme and the plugin from the server, not the warnings. The caching plugin’s advanced-cache.php file was left behind and the site went down. With the parent theme gone, the child theme reported "The parent theme is missing." We restored that morning’s backup, which put both back, and also rolled the database back to that morning. The warnings were genuine: the caching plugin was older than the release that fixed the problem.

When to get help

Stop if you have no backup and cannot tell which version was installed, if the plugin was a paid one you cannot download again, or if the site is still down after the plugin is back. Get help sooner on a shop, where a full restore can lose orders.

What a developer would check

  • Which plugins, themes and drop-in files were removed, compared with a backup.
  • The PHP error log for fatal errors from add-ons whose main plugin is missing.
  • The vulnerability record, the fixed version and the plugin’s changelog before updating.
  • Whether a files-only restore is enough, so recent orders and entries are kept.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Can I ignore the host’s vulnerability warning?
No. Check it against a database such as WPScan or Patchstack. If your version is affected and a fixed version exists, update. If there is no fix, deactivate the plugin and replace it. Do not use the hosting panel’s delete option to clear the warning.
Will reinstalling the plugin bring back its settings?
Usually, yes. Deleting the plugin’s folder from the server leaves its settings in the database, so they are picked up again when the same plugin is reinstalled. A plugin deleted from inside WordPress may have removed them.
Why did WordPress not stop the plugin being deleted?
The hosting panel deleted the files directly, outside WordPress. WordPress’s Plugin Dependencies check only applies when a plugin is deleted from the Plugins screen, and only for plugins that declare what they need.

Written by Michael Broadbridge, Founder of Webgro. First published 14 November 2026. Last checked 14 November 2026 on WordPress 7.1.