THIRDLOFT MARKETING

Website security

What the PHP2Shell Vulnerability Means for Grand Junction Businesses

The PHP2Shell vulnerability is a critical flaw in the software behind most small business websites. It did not need anyone to click a bad link. This guide explains what happened, what it could cost you, and what to check today.

Written for owners in Grand Junction, Fruita, Palisade, Clifton, the Redlands, Orchard Mesa, Delta and Montrose. We have kept the technical detail light, with links to the official advisories if you want the full picture.

What happened

What is the PHP2Shell vulnerability?

PHP is the programming language that runs a huge share of the web. On October 21, 2026, the PHP project shipped emergency fixes for two critical flaws. Security researchers nicknamed the pair PHP2Shell.

PHP sits underneath WordPress and many other website platforms. According to W3Techs, PHP runs 69.2 percent of websites whose server language is known. If your website runs on WordPress, it runs on PHP.

Both flaws carry a severity score of 9.2 out of 10. In plain terms, an attacker could take control of a vulnerable web server without logging in. Google’s security team says attackers could hijack an affected system, then steal, change or wipe its data.

Details leaked a day before the fixes were ready. Working attack code was public within days. Security firms reported scanning and attack attempts soon after.

The scale was large. Palo Alto Networks counted more than 22.6 million exposed systems that could be vulnerable. That is not a count of hacked websites, but it shows how wide the exposure was.

Some governments took no chances. Public websites in Finland, the Netherlands, Belgium and France were taken fully or partly offline while teams patched.

The fix is an update to PHP itself. You can read the official notice in the PHP security advisory. The fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

Why it matters

Why small business websites are exposed

Most security news feels like a problem for banks and big companies. This one is different, for three reasons.

No click needed

Good habits did not help

Most hacks rely on someone opening a bad link or download. This one did not. The attack goes straight at the server, so careful staff could not prevent it.

Below the plugins

Updating WordPress was not enough

The flaw lives in PHP, not in WordPress or its plugins. Clicking update in your dashboard does not touch it. Someone has to update the server.

Older sites

No easy fix for old versions

PHP 8.1 and older are no longer supported by the PHP project. Sites on those versions need a real upgrade, not just a quick patch.

Shared hosting adds another wrinkle. On a cheap plan, the host controls the PHP version, so you depend on them to act. Ask them when they patched, and get the answer in writing.

The cost

What a hacked website costs a small business

A breach rarely announces itself. These are the usual costs when a small business site is hacked and nobody notices for a while.

Leads

Forms that go quiet

Contact forms can stop working, or quietly send inquiries somewhere else. You may not notice for weeks, and those jobs go to a competitor.

Reputation

Visitors sent to scams

Hacked sites often redirect visitors to scam pages or show a warning from Google. A customer who sees that once may never come back.

Rankings

Search visibility drops

Google can flag or drop hacked sites from search results. The longer it goes unnoticed, the more of your existing rankings it costs you.

Money and data

Cleanup and exposure

Emergency cleanup is expensive, and your ads keep sending people to a broken page. If you store customer names, emails or phone numbers, those are exposed too.

Warning signs

Signs your website has been hacked

You do not need to read server logs to spot trouble. Watch for these, and act quickly if you see one.

On the site

What you might see

  • Pages, links or pop-ups that nobody on your team added
  • A site that is suddenly much slower than usual
  • A warning from Google next to your site in search results
  • Strange text or foreign words in your Google listing
  • New admin users in WordPress that nobody created
Around the site

What you might hear

  • Customers saying they landed on a different website
  • Odd emails that appear to come from your business
  • A sudden drop in calls or form leads with no clear cause
  • A message from your host about unusual activity
  • Browser or antivirus warnings when you visit your own site
  • Booking or payment tools that stop working for no clear reason

If you spot any of these, do not wait for it to clear up on its own. Call whoever looks after your site the same day.

If you are not sure who that is, that is the first thing to fix. Many owners find out during a crisis that nobody is actually responsible.

Looking ahead

Website security risks that are not going away

PHP2Shell will fade from the news. The conditions behind it will not. Three trends are worth knowing about.

AI

Flaws found faster

Google says its Gemini AI helped find these flaws. Defenders and attackers both use these tools now, so expect serious bugs to surface more often.

Deadlines

PHP 8.2 support ends soon

PHP 8.2 stops getting security fixes on December 31, 2026. Sites still on 8.2 after that date will not get a patch for the next flaw.

Speed

Less time to react

Attack code for PHP2Shell was public within days of the fix. That gap keeps shrinking, so slow patching costs more each year.

The PHP project publishes its support dates openly, and WordPress recommends PHP 8.3 or newer. If your site is older, plan the upgrade now rather than after the next headline.

Upgrades need testing, because old themes and plugins can break on newer PHP. That is a job for someone who knows your site, not a button to press on a busy Friday.

Ask your web host

Nine questions about your website security

Send these by email, so the answers are in writing. A good host will answer them quickly.

Patching

About PHP2Shell

  • Has PHP on my server been updated to a fixed version
  • On what date was it patched
  • Which PHP version is my site running today
  • Did you check my site for signs of tampering
Recovery

About the bad day

  • How often is my site backed up, and where are the copies kept
  • How quickly can you restore it if something goes wrong
  • Who do I reach after hours, and how
  • What is your plan for PHP 8.2 reaching end of life
  • Who gets told when something looks wrong on my site

If the answer to the first question is a shrug, take that seriously. Patching a server is routine work for a host that is paying attention.

If you are worried

What to do if you think your site was hit

Act fast, but do not delete anything in a panic. Evidence and backups both matter.

Do this in order

First steps

  • Tell your web host or developer and ask them to check the server
  • Make sure PHP is updated to a fixed version
  • Change your WordPress and hosting passwords after the patch
  • Remove any admin users you do not recognize
  • Restore a clean backup if pages or files were changed
Worth knowing

Patching does not undo a hack

Updating PHP closes the door. It does not remove anything an attacker already left behind, so a check for tampering still matters.

If Google has flagged your site, the warning can take a few days to clear after cleanup. Your host or developer can request a review through Google Search Console.

Keep notes as you go: what you saw, when, and who you told. It makes the cleanup faster and helps if customer data was involved.

How we handle it

How Third Loft looks after the websites we host

Since this article is about who is responsible, here is how we handle our part.

We host client sites on a private Cloudways server running on DigitalOcean. We followed PHP2Shell closely and were ready to patch the moment the fix came out. Our clients did not have to change a setting or read a single bulletin.

We also watch for trouble, keep backups we can roll back to, and upgrade PHP before old versions lose support. And because we run marketing for local businesses too, we often spot a drop in leads or rankings before the owner does.

If you would rather not think about any of this, the details are on our website maintenance and hosting page. If you are choosing a host, read our guide to hosting for Grand Junction websites.

FAQ

Frequently asked questions

What is the PHP2Shell vulnerability?

PHP2Shell is the nickname for two critical flaws in PHP, tracked as CVE-2026-109618 and CVE-2026-109619. PHP released fixes on October 21, 2026. Both flaws can let an attacker run code on a web server without logging in. That can lead to a hacked website.

Does the PHP2Shell vulnerability affect WordPress sites?

Yes, if the server has not been patched. WordPress runs on PHP, so a WordPress site on an unpatched server is exposed. The fix is a PHP update on the server, which is usually done by your host rather than inside WordPress.

Will updating my WordPress plugins fix it?

No. Plugin and theme updates still matter, but this flaw is in PHP itself. Your host or developer needs to update PHP to 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer. Then they restart the web server so the update takes effect.

How do I find out which PHP version my website uses?

In WordPress, go to Tools, then Site Health, then the Info tab, and open the Server section. Your hosting control panel usually shows it too. If you cannot find it, ask your host to tell you in writing.

My website is on Squarespace or Wix. Am I affected?

These platforms run their own servers, so patching is their job rather than yours. You cannot check or change the server software on them. If you are worried, their support teams and status pages are the place to ask.

What happens when PHP 8.2 reaches end of life?

PHP 8.2 stops receiving security fixes on December 31, 2026. After that, any new flaw found in 8.2 will stay open. Sites on 8.2 should move to 8.3 or newer before then, with testing first in case older plugins break.

Has anyone actually been hacked through PHP2Shell?

Reports were mixed in the first week. Security firms saw widespread scanning and attack attempts, and some early claims of successful hacks were later corrected. Public attack code exists, so the safe assumption is that unpatched servers will be targeted.

Can Third Loft check whether my website is at risk?

Yes. We offer a free website security check for Grand Junction businesses. We tell you what your site runs on, how exposed it looks, and whether we recommend acting soon. There is no obligation, and we will tell you if your current host already has it covered.

Next step

Not sure if your website is at risk?

Send us your website address and we will run a free security check. We will tell you what it runs on, how at risk it looks, and what we would do next.

Call us at (970) 822-0735 or request a free check below.

Free for Grand Valley businesses

Get our free local marketing toolkit

A poster maker, a website check, a Google review kit and a calendar of every big date in the valley. Tell us where to send them, and you will also get Grand Valley Marketing Notes, our short email with local marketing tips.

Free. No spam, and you can unsubscribe in one click.