All Resources
Solid Digital ·

PHP's Rough Fall: What the Latest Exploits Mean for Your WordPress Site

Tools & Technology wordpresssecuritybest-practices

If you run a WordPress site, the last 30 days have been a lot. PHP, the programming language WordPress is written in, shipped two rounds of critical security fixes. WordPress core itself landed on the U.S. government's list of actively exploited vulnerabilities. And the usual stream of plugin flaws kept coming.

Here's what happened, what to do about it this week, and why it's a big part of the reason we built Sites the way we did.

What happened

October 21: PHP2Shell

PHP disclosed two flaws in the language itself, CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell. Both are rated 9.2 out of 10 and both allow remote code execution, which is the polite way of saying an attacker can run their own code on your server. According to Palo Alto Networks' Unit 42, attackers are already using them, and its scans found more than 22.6 million internet-facing systems that could be vulnerable.

October 28: a flaw in WordPress core

WordPress 7.1.4 fixed CVE-2026-119977, a weakness in the update process that can let an attacker run code on the server during the short window while a site is updating itself. On November 3, CISA added it to its Known Exploited Vulnerabilities catalog, and confirmed attacks in the wild. Wordfence reported blocking more than 13,000 attempts against it in a single day.

November 19: seven more critical PHP fixes

Yesterday PHP released versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36, fixing seven critical vulnerabilities among more than a dozen in total. They include a session-handling flaw nicknamed phpAfterShell and a request-smuggling bug in PHP-FPM, the piece that runs PHP on most modern hosts.

Some fair context: PHP's maintainers say the critical attack paths generally need non-default configurations or uncommon setups, and as of this writing there are no public reports of these being exploited. But PHP2Shell went from patch to real attacks in under two weeks, so "not exploited yet" is not a plan. Also worth knowing: PHP 8.1 and older received no fixes at all, and PHP 8.2 reaches end of life on December 31.

Meanwhile, in plugins

The plugin ecosystem kept up its usual pace. A maximum-severity (10.0) flaw in the Bricksforge plugin came under active exploitation, and a 9.8-rated file-handling flaw was disclosed in Ultra Addons for Contact Form 7. Those are two examples from a list that grows every week.

What this means if you're on WordPress

None of this means WordPress is broken or that your site has been hacked. It does highlight how the platform is put together, and where the risk comes from.

What to do this week

  1. Check your PHP version (Tools → Site Health → Info → Server). You want 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or confirmation from your host that the fixes have been applied. If you're on 8.1 or older, you're unpatched and need to upgrade.
  2. Update WordPress core to 7.1.4 or later.
  3. Update every plugin and theme, and delete the ones you aren't using. Deactivated plugins still sit on the server.
  4. Ask your host two questions: when were the November 19 PHP fixes applied, and were PHP workers restarted afterward? The patch doesn't take effect until they are.
  5. Plan your move off PHP 8.2 before it stops receiving fixes at the end of the year.

If you're a Solid Digital hosting or support client, we're already working through this list for you.

Why we built Sites differently

We've built and maintained WordPress sites for a long time, and months like this one are a big reason we created Sites. The goal was to remove whole categories of risk instead of patching them faster.

To be clear, no platform is unhackable, and we'd be suspicious of anyone who claims otherwise. Sites still has moving parts, like form handling and the editor itself. The difference is that those parts are run and secured centrally by our team, instead of being installed on your server and left for you to keep current.

Should you move?

Not necessarily. WordPress is still the right fit for some sites, and we continue to build and support it. A well-maintained WordPress site on a good host, with a short plugin list and someone watching the updates, can be perfectly safe.

But if this month had you checking version numbers and hoping your host was paying attention, it's worth asking whether your marketing site needs that much machinery behind it. Most don't.

We handle migrations from WordPress to Sites ourselves, bringing over your pages, posts and design so you don't start from scratch. If you'd like to see what your site would look like without the patching treadmill, take a look at Sites or get in touch with our team.