Act this weekWhat happenedTwo flaws in PHP, named php2shell, were disclosed. They can let attackers crash servers, steal data or run their own code.
Who is affectedAnyone running a website or app on PHP 5.4 or later, including WordPress and Magento sites and their hosting providers.
What to do- 1Ask your web host or developer to apply the latest PHP security update now.
- 2Remember that updating a plugin or site code does not fix this; PHP itself must be updated.
- 3If you use Cloudflare, keep its firewall on and, on paid plans, confirm the Managed Ruleset is in block mode.
- 4Limit unnecessary file uploads and cap upload sizes as extra protection while you patch.
Two serious flaws in PHP, the software that runs a huge share of the web, were made public on October 21. Together they are called php2shell. Cloudflare, a company that sits in front of many websites, began blocking attacks aimed at them hours before the announcement. That help is real, but it is a backup. The actual fix is updating PHP.
What changed
Researchers from Calif.io, Wiz, OpenAI and Quarkslab disclosed the flaws, tracked as CVE-2026-109618 and CVE-2026-109619. They affect every server running PHP 5.4 or later. An attacker can send specially crafted web requests that may crash a server, expose private data, or run the attacker's own code.
Both flaws come from how PHP handles memory when something goes wrong. If a request fails partway, for example because PHP runs out of memory, PHP can later use data that was not set up properly or memory it already released. Attackers can take advantage of that mistake.
Why it matters
PHP runs almost 70% of websites, including WordPress and Magento stores. The flaws are in PHP itself, not in a single plugin or theme. So updating your site code or plugins does not fix them. Cloudflare also said the flaws leaked before the official release date, and it saw attack traffic aimed at its customers.
What Cloudflare did
Cloudflare added firewall rules, which are filters that block suspicious web traffic. Protection was switched on by default from 3:02 am UTC on October 21 for customers on all plans, including Free. It had been deployed about 9 hours before public disclosure.
The rules also look at what the website sends back, not just what arrives. That helps spot a successful attack and cuts false alarms. Cloudflare said attackers tried changing their requests to slip past the rules, and its analysts are still watching and updating them.
Who can relax a little
Sites behind Cloudflare's firewall have a safety net, and Free users need to do nothing to get it. Paid plan users should check that their setup is in block mode. Even so, Cloudflare tells customers to patch PHP. Sites that do not use PHP are not part of this story.
What to do
The alert box above lists the steps. The key one is asking your web host or developer to apply the latest PHP security update. Limiting uploads can help in the meantime, but it does not replace the fix.
What happens next
Cloudflare says it will update its rules if attackers find new tricks in the coming hours and days. Changes will appear in its public changelog. Site owners should follow the PHP advisory for affected versions and fix instructions.
The takeawayCloudflare's firewall buys time, but only updating PHP itself closes the php2shell flaws, so ask your host or developer today.