🧩
Security

Outdated plugins: the most common reason websites get hacked

19.11.2026
← All articles

When a site is hacked, owners usually suspect a weak password or a hosting problem first. In practice, the most common way into a WordPress site is different: a plugin that has not been updated for a long time. WordPress core is reviewed constantly by a large team and security fixes are applied automatically, but plugins are written by thousands of different developers with very uneven quality. A single old form, slider or upload plugin can expose the whole site, its database and even other sites in the same hosting account.

What happens after a vulnerability is disclosed

When a flaw is found, a researcher usually reports it to the developer, a fixed version is released, and the details are then published. From that moment the risk rises sharply. Attackers compare the changelog and the patched code, work out where the hole was, and start scanning thousands of sites automatically. The scanner does not care whether your site is small or famous; it only looks for the plugin folder and its version number.

That is why "my site is too small to be a target" is a mistake. Most attacks are run by bots. A bot requests known folders under wp-content/plugins/, reads the version from readme.txt, and fires a ready-made exploit if the version is vulnerable. It takes seconds, and the owner may notice nothing.

Which plugins carry the most risk

Any plugin can be vulnerable, but some types are attacked more often. Plugins that accept file uploads (forms, galleries, import tools) can let an attacker upload a PHP file if validation is weak. Page builders and sliders run on a huge number of sites, which makes them attractive targets. Abandoned plugins that have not been updated for years are a separate risk: if a flaw is found, a fix may never come. Deactivated plugins left on the server matter too, because deactivation does not remove the files and a vulnerable file can often be called directly by URL. Unused plugins should be deleted, not just switched off.

An example: a furniture shop in Tashkent

A furniture shop in Tashkent ordered a catalogue site a few years ago. It works and orders arrive, so nobody logs in to check updates. One day customers say the site sends them to an unfamiliar advertising page. The investigation shows that the homepage slider plugin had not been updated for five years and had a known vulnerability. Through it the attacker dropped a hidden PHP file in the uploads folder and used it to modify other files. Updating the plugin alone would not fix this, because the backdoor stays behind; the site needs a full cleanup and password changes first.

Checking plugin status

The Plugins screen in the dashboard shows available updates, but with SSH access WP-CLI is faster and more precise. Run these in the site folder:

wp plugin list --fields=name,status,version,update_version
wp plugin list --update=available
wp plugin list --status=inactive
wp core verify-checksums
wp plugin verify-checksums --all

The checksum commands compare files against the originals from WordPress.org. A mismatch is a warning sign. Premium plugins cannot be checked this way because their originals are not in the official directory.

A safe update routine

Delaying updates out of fear of breaking something is also risky. Make updating a routine instead:

  1. Export the database: wp db export backup.sql.
  2. Archive the site files or use the backup tool in your hosting panel.
  3. Update plugins: wp plugin update --all.
  4. Check the homepage, contact form, checkout and dashboard.
  5. Delete unused plugins: wp plugin delete plugin-name.

For larger sites, test updates on a staging copy first. On sayt.uz hosting, files and databases are managed from the ISPmanager panel, and backup questions can be raised from the sayt.uz cabinet or via support.

Auto-updates and fewer plugins

Since WordPress 5.5 you can enable auto-updates per plugin from the Plugins screen. This works well for simple plugins such as security, cache or SEO tools, while complex shop extensions may be safer with controlled manual updates. Auto-updates rely on WP-Cron, which can lag on low-traffic sites, so running wp cron event run --due-now from a server cron job helps.

Every extra plugin is extra code and another potential hole. Review your plugin list every quarter and remove what you no longer need. When choosing a plugin, look at active installs, update frequency and whether the developer answers support questions. Installing an abandoned plugin today opens the door to tomorrow's incident.

Related articles

🛡️ Securing a DLE Site: Licensing, the Admin Panel and the uploads Folder 🖱️ Clickjacking: protecting your site with X-Frame-Options and CSP 🔐 Adding Passkeys to Your Website: A Practical WebAuthn Guide 🚪 Does Changing the SSH Port Help? Myth vs Reality
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓