Can’t Patch PHP2Shell Yet? Build a Stopgap with the Controls You Own
From the source: Qualys BlogExecutive Summary PHP2Shell’s fix is to update PHP, but patching at scale is slow. Only 199,000 of 156 million PHP installations were patched in the first 12 hours after disclosure. In the meantime, Qualys’s configuration-level mitigation reduces exposure to the confirmed attack path without code changes, with or without an agent. WAF, IPS, and EDR […]
Read the full story on Qualys BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Security
How are you securing employee use of generative AI tools?
Blocking, allow-listing, DLP, enterprise licences, policy and training: what combination is working in practice?
Which security investments are you prioritising for FY27?
Identity, cloud security posture, AI security, SOC automation, resilience? Share your top two and why.
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from Qualys
Recent updates from Qualys, so you can tell whether this is a one-off or part of a pattern.
More in Security
What other companies in Security are doing. The category page shows who’s active, side by side.

