Insights

/

PHP2Shell Explained: What Small Business Owners Need to Know (and Why Our Sites Are Protected)

This week brought one of the biggest web security scares in years. If you’ve seen headlines about “PHP2Shell” and wondered whether your website is at risk, this post breaks it down i...

PHP2Shell Explained: What Small Business Owners Need to Know (and Why Our Sites Are Protected)

This week brought one of the biggest web security scares in years. If you’ve seen headlines about “PHP2Shell” and wondered whether your website is at risk, this post breaks it down in plain English: what happened, why it matters, and what it means for the sites Bold Form Marketing builds and hosts.

What is PHP2Shell?

PHP is the programming language that runs behind WordPress, WooCommerce, and a huge share of the websites on the internet. PHP2Shell is the nickname for two critical security flaws found in PHP itself, tracked as CVE-2026-109618 and CVE-2026-109619. Both were rated 9.2 out of 10 for severity.

In the worst case, these flaws let an attacker run their own code on a web server without logging in. That could mean stealing data, planting malware, or knocking a site offline.

The technical cause comes down to how PHP cleans up after a request goes wrong. If a request fails partway through, for example by hitting PHP’s memory limit at exactly the wrong moment, PHP can leave half-finished or already-freed data lying around. A carefully crafted follow-up request can then take advantage of that leftover data. Every PHP version going back to 5.4 (released in 2012) was affected.

Why it was such a big deal

  • Details leaked early. Information about the flaws got out before the official fix was ready, so the PHP team released patches on October 21, 2026, ahead of schedule.
  • Attacks started fast. Security companies reported exploit attempts within hours of the release, and some attempts were spotted days before the public announcement.
  • Government agencies weighed in. CISA, the NSA, and the UK’s NCSC all urged organizations to patch immediately.
  • Updating WordPress doesn’t fix it. This is the part most people miss. The flaw lives in PHP on the server, not in WordPress, your theme, or your plugins. Only a patched version of PHP closes the hole.

How Bold Form sites are protected

The sites we build are hosted on Hostinger’s managed hosting, where PHP is maintained at the server level by Hostinger’s engineering team. Here’s what happened on their end:

  • Attacks were blocked before the patch landed. Hostinger added firewall rules that reject requests matching the known exploit patterns.
  • A known attack route was shut off. They disabled a rarely used PHP feature (session upload progress) that one of the exploits relies on.
  • The official fix was installed everywhere. Hostinger finished rolling out PHP’s patched builds across its managed hosting platform on October 22, 2026.
  • A follow-up flaw is already covered. On October 23, PHP disclosed a third related vulnerability (CVE-2026-115560). Hostinger has confirmed its managed plans were already protected by the changes made on October 21.
  • No uptick in infections. Hostinger reports it has not seen any increase in malware or unusual activity on its managed hosting since the flaws went public.

We’ve also confirmed the patched PHP build on the sites we host. One detail worth knowing: on managed hosting, the fix is built into the PHP version a site already runs, so the version number you see may not change even though the site is patched.

Bottom line: if Bold Form built and hosts your website, there’s nothing you need to do.

Not hosted with us? Here’s what to do

  1. Ask your host if the PHP2Shell fix is installed. On shared or managed hosting, your host is responsible for patching PHP, not you. Ask them directly, and ask for the PHP build date rather than just the version number.
  2. Running your own server or VPS? You’re responsible for patching. Update to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35 (whichever matches your branch) and restart PHP.
  3. Still on PHP 8.1 or older? Those versions no longer get official fixes from the PHP project. Plan an upgrade. PHP 8.2 also stops receiving security fixes on December 31, 2026, so 8.3 or newer is the safer target.
  4. Skip the “quick fix” plugins. No WordPress plugin can patch PHP itself. Be wary of anything claiming otherwise.
  5. Look for warning signs. Unfamiliar admin users, strange redirects, new files you didn’t add, or a sudden drop in search traffic are all worth investigating.

Not sure where your site stands?

If you don’t know who hosts your website or whether it’s been patched, we’re happy to help you figure it out. Reach out at sales@boldformmarketing.com or call (314) 582-6416.

Sources: Hostinger, watchTowr, CNBC.

// Next step

Want a website that actually brings in work?

Tell me a little about your business and what you need. I'll take a look and get back to you with a straight answer.

(314) 582-6416 sales@boldformmarketing.com

Start a conversation

No pressure, no sales script.

© 2026- Bold Form Marketing LLC - Privacy policy.
Back to top