Skip to content

Dispatch, 2026-11-12, SHC Team, Cybersecurity

Two critical PHP flaws show why website updates can't wait

Filed 2026-11-12 · SHC Team

On Oct. 21, the PHP project fixed two critical security flaws in PHP, a widely used programming language behind websites and web applications. Left unpatched, they can let an attacker run their own code on a web server without logging in. The FBI urged immediate updates on Oct. 23, and federal officials now list both flaws as exploited.

What happened

The flaws are CVE-2026-109618 and CVE-2026-109619 (a CVE is the public ID number for a security flaw). The PHP project fixed both in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and urged all PHP users to update immediately. It said every PHP installation that serves web requests is at risk. On the server setup PHP rates as highest risk, a request from someone who has not logged in can trigger the attack before the website's own code even runs. PHP 8.1 and older no longer get updates from the PHP project.

The FBI's Internet Crime Complaint Center (IC3) followed with a public warning on Oct. 23. It cited a severity score of 9.2 out of 10 for both and said: "Security updates are available and should be applied immediately." If an update isn't possible right away, the FBI recommends taking the system offline until it can be fixed.

The Cybersecurity and Infrastructure Security Agency (CISA) urged organizations to patch immediately and noted the flaws are known as "php2shell." On Oct. 26, five days after the fix, CISA added both to its Known Exploited Vulnerabilities catalog, its list of flaws that have been exploited in the wild.

What changes for you

You may be running PHP without knowing it. CISA notes that PHP "is often a component of other software." That could include your website, online store, donation form or client portal, or a tool a vendor installed for you.

The fix already exists, and PHP says updating to a patched release is the only complete fix. Settings changes only reduce the risk. The real exposure is the system nobody is assigned to update: an old site a former contractor built, or a server on a version that no longer gets fixes.

What you can do

  • Find out where PHP runs. Ask whoever looks after each website and system whether it runs PHP, and which version. The FBI and CISA both say to take stock of where PHP runs, starting with anything reachable from the internet.
  • Check the version. Confirm it is 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer, or that your hosting company or software vendor has installed its patched package. PHP says Linux distributions received the fixes in advance.
  • Take it offline if it can't be fixed. If a system can't be updated now, or still runs PHP 8.1 or older, ask about taking it offline until it can be. That is what the FBI and CISA advise.
  • Look for signs of a break-in. Ask your IT person to check for them, such as PHP unexpectedly running system commands or downloading files. If they find any, the FBI asks you to isolate the system, keep the logs, and report it at ic3.gov or to a local FBI field office.
  • If you rent a server from SHC, our security hardening notes show how to check that automatic security updates are switched on. Still confirm the PHP version yourself. Security is a goal we share with you, not a promise.

Sources