Blog ·

New PHP Flaws: Fix Installed for Our Clients the Next Day, With No Reboot

Five PHP flaws rated 9.2 out of 10 let an attacker take over a server. Our team installed the fix for our clients the very next day, with no reboot.

Cyril Bouthors, founder. Managed infrastructure and DevOps since 2003. Book a Call

One well-crafted request, and a stranger runs their own code on your server. No password needed.

That is what five flaws fixed by PHP on 19 November allow, each rated 9.2 out of 10. Does your site run on PHP? Request our free cybersecurity audit, results within 1 business day.

What These Flaws Allow

  • Taking over the server by booby-trapping session files, the ones that keep your visitors logged in.
  • Hiding one request inside another (“request smuggling”), to slip past the checks in front of the site.

WordPress, Magento, PrestaShop, Drupal, Symfony, Laravel: every PHP application is concerned. No attack has been reported yet. Now is the time to fix them, not after the first attack.

What Our Team Did on 20 November

The day after the release:

  • The official fix installed wherever one exists, without waiting for the usual maintenance window.
  • No server reboot: only the PHP services were restarted, the sites stayed online.
  • Every client informed the same day on their support ticket.
  • Where no fix exists, because the system or the PHP version is no longer supported: a plan to move to a supported version, and the web application firewall in the meantime.

Our clients had nothing to ask for.

What an Open Flaw Costs

An attacker running code on your server reads your customer database, changes your pages, installs whatever they want. That is a business stopped, a data-breach notification and weeks to win back trust. The fix has existed since 19 November: every day it is not installed is a day handed to the attacker.

Is Your Platform Covered?

Unsure about your servers? Request our free cybersecurity audit: results within 1 business day.