Filed under: Cybersecurity · Website Security · October 2026

What happened

On October 21 the PHP project shipped emergency fixes for two critical flaws in PHP itself (CVE-2026-109618, CVE-2026-109619), nicknamed “PHP2Shell.” PHP is the programming language that runs on the web server behind most websites, including every WordPress, Joomla, Drupal and Magento site. The flaws let an attacker take over the server with no login. Security firms and Cloudflare saw attackers trying to exploit them before the fixes were even released, and attack traffic is still coming in.

Why it matters to your business

Your WordPress plugins and theme can be completely up to date and you can still be exposed, because this hole is in the server software underneath them. An attacker who gets in can deface your site, steal contact-form and customer data, or quietly add a hidden backdoor or a skimmer to your checkout. Most Phoenix small businesses don’t run their own web server. Your website host or web developer handles PHP, so the job this week is making sure they’ve actually done it.

What to do this week

1. Check your PHP version. In WordPress, go to Tools → Site Health → Info → Server and look at “PHP version.” A patched site shows 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer. 2. If you’re on cPanel hosting, open Select PHP Version or MultiPHP Manager to see the version, and move to 8.3 or 8.4 if you can. 3. If the version starts with 8.1, 8.0, 7.x or 5.x, you’re on a branch that is getting limited fixes or none. Ask your host or developer to upgrade it now. 4. Email your host or web developer and ask for written confirmation that your server is on a patched PHP build. If you can’t confirm that, put the site behind a web firewall such as Cloudflare, which is already blocking known attack traffic. 5. Expect brief outages: many hosts are restarting servers to apply the fix. 6. After patching, ask whoever manages the site to look for admin accounts or files that nobody recognizes.

The bigger picture

This year attackers keep hitting the layers of a website that owners can’t see, from plugins to update servers and now the language underneath. Having someone confirm patches across your whole setup, not just the parts you can see, is what keeps a fix like this from slipping through. → Proactive vs. Reactive IT Management: Lessons from Healthcare for SMBs

Not sure who’s responsible for patching your website’s server? Book a free consult → https://micro1tech.com/contact/