Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.
In plain English
PHP is a programming language that powers a huge number of websites, including many WordPress sites. Think of it as the engine in a lot of cars. When the maker finds a defect in the engine, every car with that engine needs the fix, whether or not the driver knows what an engine is.
These two flaws were rated as critical because an attacker did not need a password. If the website was reachable from the internet, the attacker could send it a specially crafted request and make the server run the attacker's commands. That is called remote code execution, and it is as bad as it sounds.
If you built a site with a tool or hired someone to host it, you may still be running PHP without having chosen it. The practical question is: which version is my host running, and have they updated it?
Words used here
- CVE
- A public ID number for a known security flaw, so everyone can refer to the same problem.
- Remote code execution (RCE)
- When an outsider can make your server run their instructions.
- Patch
- A software update that fixes a flaw.
- Known Exploited Vulnerabilities (KEV)
- A list kept by the US cyber agency CISA of flaws that attackers are actively using.
- End of life
- A version that no longer gets security fixes. Running one is like driving a car the maker will no longer repair.
What happened
CISA, the US cyber-safety agency, published a warning urging organisations to update two serious flaws in PHP (a language many websites run on). They are numbered CVE-2026-109618 and CVE-2026-109619 and nicknamed "php2shell".
CISA says the flaws affect PHP installations serving web requests, including Apache with mod_php (which PHP considers highest risk), PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. Reporting rates them CVSS 9.2 on a 10-point scale (version 4.0 of the scoring system).
On October 26, 2026, CISA updated its warning to say both flaws had been added to its list of flaws attackers are already using.
How it unfolded
- October 21, 2026
CISA publishes its alert. PHP releases fixed versions.
- October 23, 2026
CISA updates the alert with a detection rule and stronger guidance.
- October 26, 2026
CISA adds both flaws to its list of flaws attackers are already using.
Who was affected
Anyone running an affected PHP version that serves web requests. CISA urges updating to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35. CISA describes PHP 8.1 and earlier as unsupported, so they will not get these fixes. Always confirm against the official PHP and CISA pages, since details can change.
What the response was
- PHP shipped fixed releases.
- CISA urged immediate patching and published a detection rule.
- Security vendors published guidance on finding exposed systems.
What went wrong
- Very widely used server software had critical flaws reachable without logging in.
- Many sites run old PHP versions that will never get the fix.
What worked
- Fixes and public guidance appeared quickly.
- A public list of exploited flaws helped teams decide what to patch first.
What a small team should do differently
- Know which PHP (or other runtime) version your site runs, including on managed hosting.
- Ask your host in writing when they patch critical flaws.
- Plan to leave end-of-life versions before they become targets.
What you can do today
- Ask your hosting provider: "Which PHP version do we run, and have you applied the October 2026 security fixes?"
- If you run your own server, update PHP to a fixed version listed in the official advisory.
- If you cannot patch yet, or you run PHP 8.1 or older (unsupported), CISA says to take PHP-based systems offline until they can be updated. A web application firewall may give some protection in the meantime.
- Watch for PHP worker processes launching shells or downloading tools, which CISA lists as a warning sign.
The lesson to take away
If a platform you did not choose runs your product, you still own its patch level. Ask your host which versions are in use and how fast they patch.
Sources
- CISA: Critical Vulnerabilities in PHP Require Immediate PatchingCISA, updated Oct 26, 2026
- CISA Known Exploited Vulnerabilities catalogCISA
- NVD: CVE-2026-109618NIST National Vulnerability Database
Finished this one?
Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.