Act this weekWhat happenedPHP developers will release a patch today for two critical flaws that let attackers run their own code on a web server.
Who is affectedAny business whose website or web app runs on PHP, including every WordPress site, and any online store or portal built on it.
What to do- 1Ask your web host or developer today who is responsible for updating PHP on your site.
- 2Have them install the new PHP release as soon as it is out, since automatic updates will not do it.
- 3If the fix cannot go in right away, ask them to take the site offline or hide it from the public until it does.
- 4Check your site for unexpected changes after patching, and keep a recent backup.
A fix is out for two serious security flaws in PHP, the programming language behind a huge share of websites. It was released at 10AM ET on October 21. The catch is that it will not install by itself on most sites. Someone has to apply it by hand, and attackers are already moving.
What happened
PHP developers published a warning on Tuesday about two flaws rated 9.2 out of 10 for severity. Security firm watchTowr says they let an attacker run their own code on a website's server. That could mean changing a site, stealing data, and more. The firm says every PHP version from PHP 5 onward is affected.
Who is affected
The reach is wide. One security researcher estimates more than 1.3 million internet-connected hosts are likely affected. WordPress security company Wordfence warns that every WordPress site is exposed, because all of them run on PHP. WordPress reported last year that it powers more than 40 percent of the internet.
Online stores, customer portals and other web apps built on PHP are in the same position. A site that does not use PHP is outside this warning.
Why speed matters
Attackers are not waiting. Security firm Sansec said it expected mass attacks within 15 minutes of the release. Cloudflare's chief technology officer, Dane Knecht, said early attacks were already hitting PHP sites on its platform. Cloudflare has changed its firewall rules as a temporary shield until the fix is in place.
GrapheneOS, a mobile operating system developer, took its user forum offline. It said test attacks were already being built and it did not want to take the risk. PHP developer Gina Peter Banyard said patching is the only real fix, and that turning servers off might be the most sensible move until then.
What to do
The alert box above lays out the steps. The main point is to find out today who looks after PHP on your site, whether that is your web host or a developer. Wordfence stresses that automatic updates will not apply this fix.
What happens next
The European Union's computer emergency response team and the UK's National Cyber Security Centre both say companies that cannot patch right away should cut their apps off from the public internet or take them offline. Later Verge headlines say the flaws were exploited days before the patch, and that the Internet Archive was briefly forced offline. It is not yet clear how many sites have been hit, or how fast hosting companies will finish updating.
The takeawayIf your website runs PHP, make sure someone installs the new release by hand today, because automatic updates will not do it.