If you run a website, an online store or a customer portal, you may have seen the headlines this week: PHP, the language behind a huge share of the web, has just shipped emergency security fixes. Here is what happened in plain English, and what to do about it today.
So, what actually happened?
On 21 October 2026 the PHP team released updates for two critical vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed “PHP2Shell”. Put simply, they can let an attacker run their own code on a server without ever logging in. Both are rated 9.2 out of 10 for severity, and some databases score them even higher at 9.8.
The part that should get your attention: proof-of-concept code is already circulating, and Amazon has reported an exploitation attempt several days before the flaws were made public. When attackers move that fast, “we’ll get to it next quarter” is not a plan.
Does this affect me?
If any part of your business runs on PHP, then yes, it is worth checking. That includes WordPress and WooCommerce sites, Magento stores, Laravel apps and plenty of custom-built systems. The fixed versions are:
- PHP 8.5.12
- PHP 8.4.27
- PHP 8.3.36
- PHP 8.2.35
PHP 8.1 and older will not receive an official fix, so those servers need to move to a supported version. If you are not sure which version you are on, that is the first thing to find out.
What to do today
- Find your PHP version. Your hosting panel, your server or your developer can tell you in a minute.
- Take a backup first. Database and files. It takes a few minutes and makes every other step safer.
- Upgrade to a fixed version. If you use containers, that usually means pulling a freshly built image and redeploying, not just restarting what you already have.
- Test, then double-check. Load your key pages, log in, place a test order. Confirm the new version is the one actually running.
- If you cannot upgrade right now, ask your developer about temporary mitigations such as disabling session upload progress. It reduces exposure, but it is a stopgap, not a fix.
How we handled our own site
This very blog runs on PHP, so we treated it like any client system. We checked what was running, took a full backup of the database and files, moved to a patched PHP 8.3.36 release, and then verified the site and the admin area afterwards. Nothing dramatic, just a calm, repeatable routine, which is exactly how this should feel.
Where Aigumind can help
Most businesses do not have a person whose job is to watch security advisories and patch servers. That is a perfectly normal place to be, and it is where we come in. Aigumind helps businesses protect their online assets by:
- auditing which PHP versions and apps you are running across your sites and servers,
- upgrading PHP safely, with backups taken first and checks afterwards,
- keeping your cloud infrastructure and the software on it up to date as an ongoing routine, not a one-off scramble,
- watching for the next advisory, so you hear about it from us, with a plan.
If you would like a second pair of eyes on your setup, or simply want to know whether this week’s advisory affects you, get in touch. A quick check now is a lot cheaper than a clean-up later.
Sources: Laravel Forge, Help Net Security, The Hacker News.