PHP2Shell: Staying Current Is the Best Defense
On October 21, the team behind PHP released an emergency fix for two critical flaws known as PHP2Shell. PHP runs behind about 70% of websites, so the scramble started right away. Attackers were probing the flaws before a fix existed, which is what makes this a zero-day, and some organizations took their websites offline until they could patch. Five days later, CISA confirmed the flaws were being used in real attacks.
There is no way to stop vulnerabilities like this one. Nobody could have patched PHP2Shell before the fix came out, and new flaws will keep turning up in software every business relies on. What you can control is how ready you are when the next fix arrives.
What made the difference
For companies with ongoing vulnerability management in place, PHP2Shell was one more update in a routine they already run. A few things set them apart.
- They knew where PHP was running. Regular external scans of their network, including their website, showed which systems were exposed and which versions they ran. The major scanning tools added checks for PHP2Shell within days, so these companies got flagged automatically.
- They were already on current versions. The official fixes only covered versions of PHP that still get security updates. Organizations on older versions had no patch to apply, and CISA told them to take those systems offline until they could upgrade.
- Patching was already a habit. A team that applies updates every week has an owner and a process in place, so an emergency fix can go out the same day.
It wasn’t only websites, either. Attackers also used PHP2Shell to break into firewalls whose admin screens could be reached from the internet. An external scan shows you your network the way an attacker sees it, which is how exposures like that get caught.
What ongoing vulnerability management looks like
- Scan everything you have facing the internet, including your website, on a regular schedule. Internal network scanning is also very important.
- Apply patches every week. When a critical flaw is under active attack, patch it right away rather than waiting for the next cycle.
- Give every system a named owner, including the ones a vendor runs for you.
There will be another zero-day. Companies that keep scanning and patching every week will be in the best position to handle it.
Want help putting ongoing vulnerability scanning and a weekly patch routine in place? Talk to Guard Street at www.guardstreet.com/connect.





