Act this weekWhat happenedThe PHP Foundation patched two critical flaws that could let attackers run code on a server without logging in, and millions of attack attempts followed.
Who is affectedAnyone running websites or servers on PHP, plus users of Chrome, Cisco, Splunk, Atlassian, GitLab, Oracle, SolarWinds and the Duplicator WordPress plugins.
What to do- 1Ask your web host or IT provider whether your PHP version has the latest patch.
- 2Update Chrome, WordPress plugins like Duplicator, and other business software now.
- 3Install the urgent fixes first, starting with the PHP ones, CVE-2026-109618 and CVE-2026-109619.
- 4Replace any password or access key that may have leaked, and lock down anything you cannot patch yet.
Two serious flaws in PHP, a programming language behind a large share of websites, are being hammered by attackers. Cloudflare says it saw millions of attempts to exploit them after they became public. No successful attack has been seen so far. Still, some websites went offline as a precaution.
What happened
The PHP Foundation released fixes for two critical bugs, CVE-2026-109618 and CVE-2026-109619. Together they have been nicknamed PHP2Shell. Both could let an attacker run their own commands on a server without logging in. Security people call this remote code execution. In plain terms, a stranger could take control of the machine that runs a website.
Because PHP is so common, the bugs drew fast attention. Attackers began scanning the internet for sites that had not updated yet. Scanning is like trying doorknobs down a street. It does not mean a door has opened.
Why it matters
The gap between a fix and an attack is shrinking. Once a flaw is public, criminals can start testing it within hours. Waiting for proof of a break-in means waiting too long. A site that is hijacked can lose customer data, show fake pages or be used to attack others.
PHP was also not the only trouble this week. A third PHP bug, CVE-2026-115560, made the urgent list. So did fixes for Chrome, Cisco, Splunk, Atlassian, GitLab, Oracle, SolarWinds Observability and the Duplicator WordPress plugins. The report says some of these bugs need no login, some are already being used in attacks, and some still have no fix.
Who can relax a little
If you do not run a PHP site or server, the two PHP flaws do not apply to you. Even for PHP users, the report says no successful exploitation has been observed. That gives a window, but not a long one. Many small business sites run on PHP through WordPress or similar tools, so it is worth asking your provider rather than guessing.
What to do
The alert box above lists the steps. The short version: confirm the PHP patch, update your other software, and replace any password or key that may have leaked.
What happens next
Expect the scanning to continue. The report also points to a software supply-chain attack that began with a leaked key, and to AI agents being tricked into following harmful instructions. Details on how many sites are still unpatched are not given. Neither is which of the listed bugs are already being exploited. Those answers will shape how urgent each update becomes.
The takeawayAsk your web host or IT provider today whether the PHP fixes are installed, and do not wait for proof of an attack.