1. News
  2. Alerts
  3. PHP · Security update
AlertPHP · Security update2 min read

PHP fixes two critical flaws that let attackers take over servers

PHP shipped fixes for two critical flaws that could let attackers run code on a web server with no login. Any site running PHP should update.

By the Dashline deskSource: Techmeme
PHP fixes two critical flaws that let attackers take over servers
Photo: Victorgrigas, CC BY-SA 3.0
Act this week
What happenedPHP released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two critical flaws that can let attackers run code remotely without logging in.
Who is affectedAnyone running PHP on a web server, including sites and portals built on PHP tools such as WordPress, and the hosts and developers who maintain them.
What to do
  1. 1Find out which PHP version your website, portal or web app runs.
  2. 2Ask your host or developer to update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
  3. 3Take a backup before the update, then test your site afterward.
  4. 4If you cannot update right away, ask your host about interim protection.

PHP has released security updates for two critical flaws. Either one could let an attacker take control of a web server over the internet without logging in. The project says every web-serving PHP deployment is affected and urges all PHP users to update.

What changed

PHP is a programming language that runs a large share of websites behind the scenes. The new releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Each one fixes both vulnerabilities.

The flaws are called unauthenticated remote code execution bugs. In plain terms, a stranger could send a request to a vulnerable server and make it run the stranger's commands. No password or account is needed. That is why they are rated critical.

Who it affects

Anyone whose website, customer portal or web app runs on PHP. That includes sites built on PHP tools such as WordPress. Most owners will not run the server themselves, so the real work falls on hosting companies and developers.

Readers who only visit websites, or who use a site built on something other than PHP, have little to worry about from this alert.

What to do

The alert box above lists the steps. The short version: find out which PHP version your site uses, then ask your host or developer to move to one of the fixed versions this week.

What is not known yet

The material does not say how the flaws work in detail, whether attackers are already using them, or which older PHP versions are left without a fix. Check with your host or developer for the latest guidance.

The takeaway

If your site runs PHP, ask your host or developer to install the fixed version this week.

More articles

You should really read these.

Next step

Let’s talk