By Harsimran (Harry) Singh, Director, Sites Crafted. Updated 22 October 2026.
On 21 October 2026 the PHP project released emergency fixes for two critical security flaws nicknamed “php2shell”. If your business has a website, there is a good chance it runs on PHP, and a site built some years ago may be running a version that will never get a fix. This page explains what happened without the jargon, how to check your own site in a few minutes, and what to do next. Facts about the flaws are as of 22 October 2026.
What is php2shell?
PHP is the programming language that powers a large share of websites. The two flaws, tracked as CVE-2026-109618 and CVE-2026-109619, are both rated 9.2 out of 10 (critical). Both can allow an attacker anywhere on the internet to run their own code on your web server without needing a password. The problem sits in PHP itself, so it is not caused by something you installed or a mistake in your website. The official details are in the PHP advisory, and Tenable has a readable question and answer page.
Security firms are reporting early attack attempts, and exploit code is circulating. Treat it as urgent, but this is a “check and update this week” job, not a reason to panic.
Does my website run on PHP?
Probably, if any of these are true:
- It is built on WordPress, WooCommerce, Joomla, Drupal or Magento. All of them run on PHP.
- You log in to a dashboard at an address ending in
/wp-admin. - It sits on ordinary cPanel or Plesk hosting.
Sites on hosted builders such as Shopify, Wix or Squarespace run on the platform’s own servers rather than a hosting account you manage, so there is usually no PHP setting for you to change. If in doubt, ask the platform. If you are not sure what your site is built on, ask whoever built it, or send us the address and we will tell you.
How to check your PHP version
- WordPress: log in, go to Tools, then Site Health, then the Info tab, and open “Server”. The line “PHP version” is what you want.
- cPanel: under Software, open “Select PHP Version” or “MultiPHP Manager”.
- Plesk: go to Websites & Domains, then PHP Settings.
cPanel and Plesk often show only the branch (for example 8.3), not the exact patch number. The fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, so a branch name alone does not prove you are safe. Ask your host for the exact build. Typing php -v on a server is not proof either, because the web server can use a different PHP build from the command line.
Who is responsible: you or your host?
- Shared or managed hosting: your host installs the fixed PHP build. You usually cannot do it yourself. Your part is to confirm that it has happened. cPanel and Plesk have both released updates, so hosts can apply them.
- Your own VPS or dedicated server: it is on you or your IT provider. Update PHP, then restart PHP so the new code actually loads. Until a restart, the old code keeps running.
A message you can copy and send to your host or web designer
Subject: php2shell (CVE-2026-109618 / CVE-2026-109619) and my website
Hi,
Please confirm the following for my website [yourdomain.com.au]:
- Which PHP version and exact patch build is my site running right now?
- When will the fixed build (8.5.12, 8.4.27, 8.3.36 or 8.2.35, or a vendor backport for older branches) be installed, or when was it installed?
- Have the PHP workers been restarted since the update?
- What interim protection (such as firewall rules) is in place until then?
- Have you checked my account for signs of compromise?
Please reply by [date]. Thank you.
[Your name, business, phone]
Why old websites are the real risk
PHP released fixes for the 8.5, 8.4, 8.3 and 8.2 branches. PHP 8.1 and older are end of life and get no official release. PHP published minimal source backports for 7.4, 8.0 and 8.1, but those are for people who build PHP from source, which is not how most small business sites are hosted. Some hosting and long-term-support vendors do ship their own backported builds, so ask yours.
That matters for small business owners, because websites built five or more years ago were often set up once and left. If yours is on PHP 8.1 or older and your host has no backport, the realistic fix is moving the site to a supported PHP version. Also note that PHP 8.2 reaches end of life on 31 December 2026, so a site on 8.2 is patched today but needs a plan to move to 8.3 or newer. You can see the current schedule on the PHP supported versions page.
What a safe PHP update looks like
Changing PHP versions is not a one-click job to do blindly. Old themes and plugins can break on a newer version, and per-version settings do not always carry across. We have seen a default memory limit take sites down after a version switch. A careful update goes like this:
- Back up the files and the database, and confirm you can restore from the backup.
- Use a staging copy of the site where you can test without risking the live one.
- Update WordPress, the theme and the plugins first, and remove any you no longer use.
- Change the PHP version on the staging copy, then test the pages that matter: forms, checkout, bookings, logins.
- Check PHP settings such as memory limit still look right for the new version.
- Repeat on the live site at a quiet time, check it again, and keep the backup for a few days.
If something breaks, it is far better to find out on the staging copy.
Signs a site may already be compromised
- Unknown files in your web folders, especially .php files inside the uploads folder
- New administrator users or plugins you did not install
- Unexpected scheduled tasks (cron jobs)
- Spam pages, odd redirects, or a Google “This site may be hacked” warning
- Spikes in server load or outgoing traffic, or a suspension email from your host
If you see any of these, do not just delete the strange file. Change your passwords (hosting, WordPress admins, database, SFTP), restore from a clean backup if you need to, scan the site, and then patch. You can also report a serious incident to the Australian Cyber Security Centre at cyber.gov.au.
Protection while you wait for the fix
- Put the site behind Cloudflare, proxied. Cloudflare has deployed firewall rules for these flaws on all plans, including Free, but they only protect traffic that passes through Cloudflare (the orange cloud). A DNS-only (grey cloud) record gets nothing. Read the Cloudflare announcement.
- Keep recent backups, stored away from the server itself.
- Remember it is only a stopgap. PHP says plainly: there are no complete mitigations, and updating is the only safe choice.
How Sites Crafted can help
Sites Crafted is a Brisbane web studio working Australia-wide. We build WordPress sites and also look after them, which covers core, theme and plugin updates, backups, uptime monitoring and SSL, with a person to call when something breaks. For this situation we can:
- Check what your site runs on and which PHP version it uses.
- Update the site safely, following the steps above, or build a fresh site if the old one is too out of date to update sensibly. See our WordPress development and services pages.
- Take over the ongoing updates and backups, so this does not catch you out again.
To start, send us your website address through the contact form (choose “Fixes or updates to my website”), email info@sitescrafted.com, or call 1300 502 000. You get a price and a timeline back, not a pitch deck.
FAQ
What is php2shell? It is the nickname for two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, announced on 21 October 2026. They can allow unauthenticated remote code execution on a web server running PHP.
Is WordPress affected? The flaw is in PHP, not WordPress, but WordPress runs on PHP, so a WordPress site on an unpatched PHP version is exposed. Updating WordPress alone does not fix it.
What PHP version do I need? PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later. PHP 8.1 and older receive no official fix, so those sites need to move to a supported version, or use a vendor backport.
Can I update PHP myself? On a server you manage, yes. On shared or managed hosting, the host installs the fixed build, and you can often choose the PHP branch in cPanel or Plesk. Back up first and test afterwards.
Do Shopify, Wix or Squarespace sites need patching? Usually there is nothing for you to change, because the platform runs the servers rather than a hosting account you manage. If in doubt, ask the platform.
My site is old. Should I patch it or rebuild it? If the theme and plugins are current and the site works on a supported PHP version, an update is usually enough. If it only works on PHP 8.1 or older, or depends on abandoned plugins, a rebuild is often the safer option. We can tell you which applies once we look at it.