Critical PHP Flaws Under Active Attack: Patch Now to Avoid Site Takeover
Many websites may show error pages today after PHP released an emergency update for two critical vulnerabilities. Krebs on Security reports that nearly 70 percent of websites need to update their core software. The flaws let an attacker run code of their choosing on a vulnerable server, which can mean full control. Experts say working exploits exist and the bugs are already being used in the wild.
PHP powers a large number of web publishing systems, including Drupal, Magento, Joomla and WordPress. The flaws are tracked as CVE-2026-109618 and CVE-2026-109619, and they affect all web servers running PHP 5.4 or later. Wiz says every PHP version released in the last decade is affected by at least one of them. Fixes are available in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Censys counted about 2.58 million internet-facing hosts and 54.9 million web properties running PHP.
Reuters reports that government websites in Europe and elsewhere went offline after disclosure. Cloudflare says it has seen some exploitation and added web application firewall rules at 3:02 am UTC to block attack traffic. It warned the bugs could cause denial of service, remote code execution and data exposure. Wiz expects mass exploitation to install web shells, which give attackers a web-based panel to remotely control compromised sites.
Wiz compares the situation with Log4Shell in 2021 and expects organisations to struggle to patch for some time, because PHP is so deeply embedded in applications. The researchers say the flaws had existed for decades, but frontier AI models helped reduce the barrier to building a working exploit. Ubuntu has already released updated PHP packages, and the SANS Internet Storm Center is tracking other platforms shipping fixes. The source describes this as a fast-moving story.
Why it matters
Because PHP sits underneath WordPress, Joomla, Drupal and Magento, small businesses are exposed even if they never installed PHP themselves, and may depend on a host or agency to patch. The usual assumption that updating the website application keeps you safe breaks here, since the flaw is in the underlying language runtime. With exploitation already under way, the decision is no longer when to schedule patching but who is responsible for it right now.
What to do
- Update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or the matching vendor package such as Ubuntu's updated PHP.
- Ask your hosting provider or web agency to confirm in writing which PHP version your sites run and when it was patched.
- Search web directories for unexpected files that could be web shells, and review servers for signs of unauthorised remote control.
- Confirm your web application firewall, such as Cloudflare, has the new rules for these flaws enabled as a stopgap.