← All articles

WordPress Vulnerabilities Being Exploited Right Now: What Small Businesses Need to Check

A small-business owner calmly reviewing her WordPress website on a laptop

If your WordPress site uses plugins for page building, forms, events, or backups, take a few minutes this week to check that everything is up to date, and remove anything you no longer need.

Recent reports show why that routine matters. In September 2026, security researchers reported critical vulnerabilities in familiar WordPress plugins, including some that attackers were actively exploiting. In October, a vulnerability in a backup plugin affected around 600,000 WordPress sites. And in November, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) flagged a WordPress remote code execution flaw as actively exploited in attacks.

This is not a reason to panic. It is a reminder that a small business website can be reached by automated scanning bots that look for sites running vulnerable software. Those bots do not need to know who owns your business. If your site has the affected component and it hasn’t been patched, it may be found and targeted automatically.

What recent WordPress vulnerability reports mean

The incidents are worth noting because they involve plugins used for everyday website tasks:

  • Elementor Pro: In September, Wordfence and BleepingComputer reported that attackers were actively exploiting a critical vulnerability to take over WordPress sites. Wordfence’s report has more detail.
  • The Events Calendar: Wordfence reported two critical vulnerabilities in September. Both were unauthenticated vulnerability chains that could lead to remote code execution. Read Wordfence’s report.
  • Super Forms: In September, Wordfence reported that a critical vulnerability in the plugin was actively exploited. See the report.
  • Backuply: In October, Wordfence reported a SQL injection vulnerability affecting around 600,000 WordPress sites. Read the Backuply report.
  • WordPress remote code execution flaw: In November, CISA flagged a WordPress flaw as actively exploited in attacks. BleepingComputer covered the alert.

These reports cover different issues, but the practical lesson is consistent: plugins that handle common business needs still need attention. A tool working normally on your site does not mean it is safe to leave unmaintained.

Business owner checking a list of installed WordPress plugins and their update notices

How a plugin vulnerability can reach a small business

When researchers disclose a vulnerability and a fix becomes available, attackers may look for websites that have not installed it. Automated scanners can send requests to many sites and look for signs of vulnerable software. A site does not need to be famous or high-traffic to be scanned.

That is why “I’ll update it later” is more than a housekeeping delay. While a vulnerable plugin remains installed, the site may continue to expose the weakness addressed by a patch. Some reported attacks have started within days of a patch or disclosure. You do not need to understand the technical details of every WordPress vulnerability to act on an update notice: you need a reliable process for checking and applying updates.

A security plugin or firewall may help block some malicious requests, but it should not be treated as a substitute for updating the vulnerable software. If attackers may already have accessed the site, applying an update alone also does not establish that the site is clean.

Is my WordPress site at risk?

Start by checking whether any of the plugins named in these reports, or other plugins you use, are installed and what versions they are running.

  1. Sign in to WordPress and open Plugins → Installed Plugins.
  2. Look for Elementor Pro, The Events Calendar, Super Forms, and Backuply.
  3. Check the update information shown in WordPress, then consult the plugin’s own update notice if you need to confirm which release fixes the issue.
  4. Apply available updates promptly. If you rely on a developer to manage the site, ask them to confirm what is installed and whether it has been updated.
  5. Review your themes and the WordPress core for pending updates as well.

Make a simple list of the plugins your website actually needs. If you find an unfamiliar plugin, check with the person who built or manages the site before changing it. A plugin may support a form, booking feature, or page layout that your business relies on.

A small-business owner reviewing a plugin inventory and update notices on a laptop

What to check this week

Update the software you use

Install pending updates for WordPress, plugins, and themes. For a business-critical site, consider asking your site manager to test updates before applying them to the live site. After an update, check key functions such as contact forms, booking pages, and checkout.

Delete plugins you no longer need

Deactivating a plugin is not the same as removing it. If a plugin is no longer needed, delete it, after confirming it is not supporting a feature your site depends on. Fewer unnecessary components mean fewer things to keep track of and maintain.

Look for plugins that appear abandoned

If a plugin has not received updates or you cannot confirm it is still maintained, do not leave it in place indefinitely without a plan. Ask your developer or hosting provider whether it should be replaced. For a broader maintenance routine, see our WordPress security checklist for small businesses.

Watch for signs the site may already be compromised

A plugin vulnerability does not always leave an obvious sign, and any one symptom can have another explanation. Still, investigate if you notice:

  • An administrator account you do not recognize.
  • Unexpected pages, links, or website changes.
  • Redirects you did not set up.
  • Files you do not recognize, or unusual file changes.
  • A warning from your hosting provider, Google, or a browser.
  • Forms, login pages, or other parts of the site behaving unexpectedly.

If you find something suspicious, avoid assuming that an update or a quick deletion has resolved it. A site may have unauthorized access routes or malicious code beyond the plugin that was initially vulnerable. Our guide to signs your WordPress site may be hacked explains what to check next.

Why restoring a backup is not a fix by itself

Backups are important for recovery, but restoring one does not automatically secure a site. The backup might contain compromised files or data, and restoring it may bring the problem back. A restore also does not necessarily remove every unauthorized account or close the route an attacker used.

The Backuply report is a useful reminder that backup tools themselves need updates and care. Before relying on a restore, confirm that the backup is suitable and investigate the original entry point. After restoring, check the site’s software and access, and look for signs of compromise. WordPress’s backup guide explains the role of backups in site maintenance.

If your site shows signs of compromise

Take the concern seriously, but work through it methodically. Save a copy of the current site for investigation, contact your hosting provider or a qualified WordPress security professional, and avoid deleting files you cannot identify. A thorough recovery may need to check site files and the database, remove backdoors, review administrator and hosting access, and harden the site before it returns to normal use.

If Google has flagged the website, cleaning the site is the priority before requesting a review. Our guide to removing the Google “This site may be hacked” warning covers that process. The Hack Remover helps businesses clean hacked WordPress sites, address access risks, and harden them after cleanup.

A small-business owner checking a laptop alongside a separate backup drive

A practical next step

You do not need to follow every security headline to protect your website. Keep an inventory of the plugins you use, install updates promptly, remove software you no longer need, and investigate unexpected changes. If a plugin named in a recent report is on your site, check it now rather than putting it off.

For more help maintaining your site, visit our WordPress security checklist. If you already see signs of a compromise, start with our guide on what to do first after a WordPress site is hacked.

Talk with RachelAI receptionist · 613 706 8145