← All articles

Is WordPress Safe? Recent Vulnerabilities Explained for Business Owners

Ken Cox · November 19, 2026

Short answer: WordPress can be run safely, and it is also a lot of work to keep that way. For a small business owner, those two things are both true.

This is not a hit piece on WordPress, and it is not a claim that your site has been hacked. It is a plain-English walk through what the public record actually says about WordPress and PHP security in 2025 and 2026, and what that means if you run a shop, a salon, or a trades company on a simple WordPress site.

What "safe" would have to mean

If "safe" means "the core software is taken seriously, and problems get patched," WordPress has a real security team and it does ship fixes. Several of the sources in this article are official WordPress.org release notes.

If "safe" means "a busy owner can leave the site alone for six months and not think about it," that is a different question. Most of the risk is not a mysterious flaw in the WordPress logo. Most of the risk is the plugins and the update treadmill around them.

The year in numbers, with a source

Patchstack's State of WordPress Security in 2026 report, which covers 2025, is the clearest public snapshot we used for totals:

  • 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, a 42% increase compared to 2024
  • 91% were in plugins, 9% were in themes, and 6 were in WordPress core, which Patchstack described as low-priority issues
  • 1,966 (17%) had a high severity score, meaning they were likely to be exploited in automated mass-scale attacks
  • 46% of vulnerabilities did not receive a fix from the developer in time for public disclosure
  • For heavily exploited, high-impact vulnerabilities, Patchstack's weighted median time to first exploit was 5 hours, and it said approximately half of high-impact vulnerabilities get exploited within 24 hours

Source: Patchstack, State of WordPress Security in 2026, date updated February 25, 2026.

Two things those numbers do not mean. They are not a count of hacked sites. And a higher disclosure count can also mean more researchers are looking. Even with that caveat, the practical point for a shop owner is hard to dodge: the work lives in plugins, patches are often late, and the serious holes can be under attack the same day you hear about them.

What actually happened, recently and in public

Here are documented incidents and releases, not rumors. The links below are the original reports.

Post SMTP, November 2025. A critical flaw (CVE-2025-11833) in the Post SMTP plugin, installed on more than 400,000 WordPress sites, let unauthenticated attackers read email logs, including password-reset links, and hijack administrator accounts. Attacks started November 1, 2025. Wordfence said it blocked over 4,500 exploit attempts. The issue was fixed in version 3.6.1. Source: BleepingComputer, November 4, 2025.

WordPress 7.0.2, July 17, 2026. A core security release that fixed a SQL injection and a REST API issue leading to remote code execution (CVE-2026-63030 and CVE-2026-60137). Because of the severity, WordPress.org enabled forced updates through the auto-update system. Source: WordPress.org, July 17, 2026.

Super Forms, mid-2026. A critical unauthenticated file-upload bug (CVE-2026-14894) could lead to remote code execution. It was fixed in version 6.3.314. Attacks were reported starting July 14, 2026. Wordfence later said it blocked more than 250,000 exploit attempts. Source: The Hacker News, September 4, 2026.

Elementor Pro, August 2026. A critical file-upload flaw (CVE-2026-32475) in Elementor Pro, a plugin with more than 6 million active installations, was patched on August 19 and exploited the same day. Attackers could upload PHP files through a form's file-upload field and take over the site. Wordfence reported blocking more than 190,000 attempts. This matters in part because Elementor is widely used: W3Techs, on November 18, 2026, put Elementor on 31.5% of WordPress sites. Source for the incident: BleepingComputer, September 3, 2026.

PHP, October 21, 2026. PHP released security updates for every supported version — including 8.5.12, 8.4.27, 8.3.36, and 8.2.35 — fixing two critical vulnerabilities (CVE-2026-109618, CVE-2026-109619) that can allow unauthenticated remote code execution. The announcement said there are no complete mitigations and "updating is the only safe choice." Source: PHP 8.5.12 announcement. WordPress sites run on PHP, so this is a WordPress-owner problem even though it is not a WordPress-core bug.

WordPress 7.1.4, October 28, 2026. Another core security release. The official notes include a weakness in the upgrade process that can lead to remote code execution during the upgrade window, plus multiple stored cross-site scripting issues and other fixes. WordPress.org recommended updating immediately. Source: WordPress.org, October 28, 2026.

PHP, November 19, 2026. The PHP project shipped another security release for all supported versions, with the highest severity marked critical. It also said the issues rated critical "require either non-default configuration or uncommon setups." That caveat matters. This is evidence that the releases keep coming, not a claim that every default install was about to be taken over. Source: php.net 2026 news archive.

One more quiet fact, because a lot of small business sites are not on current PHP at all: PHP 8.1 reached end of life on December 31, 2025. PHP 7.4 ended on November 28, 2022. PHP 5.6 ended on December 31, 2018. Unsupported branches do not get those security fixes. Source: php.net unsupported branches.

So… is it safe enough for a shop site?

It can be, if someone is really on it: backups, updates, a short plugin list, current PHP, and a person who notices when a new admin user appears.

The problem is who that someone is. If it is you, between jobs, WordPress is not "unsafe" so much as it is unsuited to your actual life. If it is a 9-to-5 developer you have to chase, you are safe only when they have time. If it is nobody, you are hoping.

WordPress is still the most-used CMS in the world — W3Techs had it at about 57% of sites with a known CMS on November 18, 2026, which is 38.5% of all websites. Plenty of careful people run it well. "Popular" and "doesn't need watching" are not the same thing.

This is going to keep coming. The last twelve months were not a one-off bad semester. They were a series of plugin holes, core security releases, and PHP patches, some of them exploited in hours.

If you don't want to be the person who keeps up

You have two honest paths.

Stay on WordPress, and make the maintenance real: a backup you have tested, updates that actually run, fewer plugins, current PHP, and a person whose job it is. The first-aid version of that list is in our article on what to do if a WordPress site gets hacked.

Or get off the treadmill. If your site is a simple Main Street site, you can hand it to a web developer who is always there and stop thinking about plugins.

That's what InLink is for. Go to inlink.com. Give Link, the AI web developer, your URL. It copies or moves the site, up to 50 pages, with a URL, forms, and a leads inbox. You change the site by asking. It's $99 a year, with no monthly bill; extras such as a domain name are priced before you buy. Code INLINKBETA makes the first 6 months free while its uses last.

Put Link on your team. No more 9-to-5 web developers, and no more Sunday-night update sessions. You're a business owner. You shouldn't have to be a WordPress security analyst too.

Want off the WordPress treadmill?

Give Link your URL. It copies or moves the site, up to 50 pages, and you change it by asking. $99 a year.

See how it works