๐Ÿ“ž Call Now: (810) 742-2409

Security Alert ยท 7 min read

Critical PHP Flaw Lets Hackers Take Over Websites โ€” Here's What to Do Today

On October 21, the PHP project released emergency fixes for two critical flaws that can let an attacker run code on your web server with no password. If your website, online store, or business app runs on PHP, this is a call-us-today kind of problem.

Critical PHP vulnerability alert A cracked shield over a code symbol, a CVSS 9.2 critical badge, and the four PHP versions that contain the fix. </> CVSS 9.2 CRITICAL PHP VERSIONS WITH THE FIX 8.5.12 8.4.27 8.3.36 8.2.35

If you run a website, an online store, a customer portal, or an in-house web app, there's a good chance it runs on PHP, the programming language behind a large share of the web, including WordPress. On October 21, 2026, the PHP project shipped security updates for two critical flaws. Here's what that means in plain English, who needs to act, and how we can take it off your plate.

What Happened

Critical ยท CVSS 9.2 of 10

The PHP project disclosed two vulnerabilities, tracked as CVE-2026-109618 (a flaw in how PHP handles running out of memory) and CVE-2026-109619 (a flaw where PHP can act on stale information left over from an earlier request). Both are rated critical and both allow unauthenticated remote code execution.

Translated: someone on the internet, with no login and no password, could potentially make an unpatched server run commands of their choosing. That's the most serious category of web server flaw there is. It's not "somebody might see a page they shouldn't." It's "somebody might take over the machine."

The fixes shipped in these PHP versions. If your server runs one of them (or newer), you have the fix:

8.5.128.4.278.3.368.2.35

Source: the PHP project's official announcement. PHP's advice is that updating is the only complete fix.

Who Is Affected

Any website or application running on an unpatched PHP version. That includes:

  • WordPress, Joomla, Drupal, Magento and other PHP-based content systems and online stores
  • Custom business web apps, customer portals, intranets and booking or quoting systems
  • Sites on a VPS, a dedicated server, or a server sitting in your own office
  • Sites on shared hosting where nobody has confirmed the PHP version since the announcement

Sites built on Wix, Squarespace or Shopify are not directly exposed, because those companies run the servers and handle patching. If you also run a separate blog, portal or older app on PHP, that part still needs checking.

Here's the catch most people miss: this fix lives on the server, not inside your website. Updating WordPress, your theme, or your plugins does not patch PHP. Whoever manages the server has to do it, and then restart the PHP service so the fix actually takes effect.

Running an older version? According to PHP's advisory, PHP 8.1 and older get source patches only, with no packaged update to simply install. If that's you, the real fix is moving to a supported PHP version, and that can break older plugins and apps, so it needs testing and a plan. This is exactly the job people put off, so please don't.

Why Speed Matters: The Clock Starts at Release

A public security fix is a roadmap. Once the patch is out, attackers can compare the old code with the new code to see exactly what was broken, and automated tools start sweeping the internet for servers that haven't updated yet. Those tools don't care whether you run a Fortune 500 company or a three-person shop. The pattern usually looks like this:

  1. Day 0Patch released and the flaw becomes public
  2. HoursAttackers study the fix to see what changed
  3. DaysAutomated scans hunt for unpatched servers
  4. After thatUnpatched sites get hit, often in bulk

Every day your server stays unpatched is a day you're relying on luck. The good news: a patch applied now is quick and inexpensive compared with cleaning up after a break-in.

What to Do Today

  1. Find out which PHP version you're running. Ask your host or IT provider in writing, or call us and we'll look it up for you.
  2. Confirm the October 21 fixes are installed. Look for PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer. "We handle updates" isn't an answer, so get the version number.
  3. Back up first, then update and restart. The PHP service has to be restarted for the fix to take effect, and a backup means you can undo it if something misbehaves.
  4. Plan the upgrade if you're on an unsupported version. The sooner the compatibility testing starts, the sooner you're off the list.
  5. Watch for warning signs over the next few weeks. New or oddly named files in your site folders, unfamiliar admin users, unfamiliar scheduled tasks, your site redirecting visitors somewhere strange, or unexpected email going out from your domain.

Try It: Am I at Risk?

Answer three quick questions about your site and we'll give you a general idea of how urgent this is for you.

PHP Vulnerability Risk Check

1. What does your website or web app run on?

2. Who manages the server it runs on?

3. When was the server's software (including PHP) last updated?

This is a general guideline, not a security audit. For a definite answer, send us a message or call (810) 742-2409 for a free PHP check.

How Computer Solutions Etc. Can Help

Patching is routine work for us. We patched our own hosting servers the same day the fix was released, and we use the same process for clients. Here's what we can do for you:

  • Free quick PHP check. We find out which PHP version your site or server runs and tell you plainly whether you're exposed.
  • Patch PHP on your server. Backup first, then update, restart the services and confirm the fixed version is live.
  • Update affected software. That covers WordPress, other CMS platforms, plugins, themes and the other pieces that depend on PHP.
  • Migrate off unsupported PHP versions. We test your site and plugins on a current version, fix what breaks, and switch over with minimal downtime.
  • Check for signs of compromise. We look for odd files, unknown users and scheduled tasks, and unexpected outbound email.
  • Keep it from happening again. Managed updates, monitoring and backups so the next critical patch gets handled without a scramble.

Why You Should Call Us Today, Not Next Week

  • It needs no login. Attackers don't have to trick you or guess a password. They just have to find your server.
  • Automated tools do the hunting. Small businesses get swept up too, because the scanners check everyone.
  • A breach costs far more than a patch. Think of cleanup, lost customer trust, a defaced or blocked site, search engines flagging you, and your server sending spam that gets your business email blocklisted.
  • The longer you wait, the bigger the job. An old PHP version gets harder to move off with every month it sits there.
  • One call settles it. The free check takes little time, and you walk away knowing where you stand.

Get your free quick PHP check

Call or message us and we'll check which PHP version your site or server runs, tell you whether you're exposed, and lay out the fix if you are. No charge for the check.

For the IT-Minded

If you manage your own servers, here's the short version.

Details and affected versions

CVE-2026-109618 (out-of-memory state corruption) and CVE-2026-109619 (stale request state). Both are unauthenticated remote code execution, scored CVSS v4.0 9.2. Fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. For PHP 8.1 and older, the advisory points to source patches only. PHP's interim settings are stopgaps. Updating is the only complete fix.

How to check your version

The command line version can differ from the version your website actually uses, so check the version your web server or PHP-FPM pool runs. On cPanel/WHM, MultiPHP Manager shows the version per domain.

php -v
# cPanel/WHM (EasyApache 4): list the PHP version assigned to each domain
whmapi1 php_get_vhost_versions
How to apply the fix

Update the PHP packages from your vendor's repository, then restart PHP so the new code is loaded. Back up first, and verify the version afterward.

# cPanel/WHM (EasyApache 4, example for PHP 8.3)
dnf update 'ea-php83*'
/scripts/restartsrv_apache_php_fpm

# Debian/Ubuntu (example)
apt update && apt upgrade
systemctl restart php8.3-fpm

Some distributions backport the fix without changing the version number, so check the package changelog for the CVE IDs if the version looks old.

Common Questions

Is my WordPress site affected?

WordPress runs on PHP, so it's exposed if the server underneath it runs an unpatched PHP version. The fix has to be applied to PHP on the server by your host or IT provider. Updating WordPress itself or its plugins does not fix it.

Do I need to do anything if I use Wix, Squarespace or Shopify?

Not directly. Those platforms manage the servers behind your site, so patching is their responsibility. If you also run anything else on PHP, such as a separate blog, a customer portal or an older business app, that part still needs checking.

My hosting company says they handle updates. Am I covered?

Often yes, but confirm it. Ask your host in writing which PHP version your site runs and whether it includes the October 21 security fixes. Hosts patch on different schedules, and some plans leave the PHP version up to you.

What does "unauthenticated remote code execution" mean?

It means someone on the internet could potentially make your server run commands of their choosing without logging in or having any password. It's the most serious category of web server vulnerability.

What if I'm running PHP 8.1 or older?

According to the PHP project's advisory, PHP 8.1 and older get source patches only, with no packaged update. The practical fix is to move to a supported PHP version, which may require testing your site and its plugins first. We can plan and handle that migration.

How does the free PHP check work?

Call us at (810) 742-2409 or send a message. We check which PHP version your site or server is running and tell you whether you're exposed, at no charge.