SECURITY ALERT

PHP2Shell: patch your PHP server now

Two critical flaws, one request to take over

Photo: PiDatacenters / CC BY-SA 4.0 / Wikimedia Commons

WHAT HAPPENED

Emergency PHP fixes on Oct. 21

PHP shipped patches for CVE-2026-109618 and CVE-2026-109619, nicknamed PHP2Shell. Both are rated critical.

WHY IT IS BAD

No login needed

A single crafted request can run code on the server before any of your own app code, plugins or login page even load.

WHO IS EXPOSED

Any PHP web server

PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed. Apache with mod_php is at the highest risk.

Photo: Derrick Coetzee / CC0

FIXED VERSIONS

8.5.12, 8.4.27, 8.3.36, 8.2.35

Anything older in those branches is affected. PHP 8.1 and earlier are end of life: upgrade or use a vendor backport.

WORDPRESS USERS

Check Tools, Site Health, Info

Open the Server section and read your exact PHP version. Compare it with the fixed versions.

ASK YOUR HOST

One yes-or-no question

"Have you deployed the PHP2Shell fixes on my server?" Do not accept a vague answer.

CANNOT PATCH TODAY?

A stopgap, not a fix

session.upload_progress.enabled=0 plus a restart of every PHP worker blocks one known attack path. The UK NCSC says go offline if you cannot fix it.

EXTRA LAYER

Turn on your CDN firewall

Cloudflare says it has deployed initial rules for known exploit paths on all plans, including free.

Photo: Carl Lender / CC BY 2.0

AFTER PATCHING

Look for signs of a break-in

New admin users you did not create, strange files in uploads, or spam pages showing up in Google.

FULL GUIDE

The complete PHP2Shell checklist

Fixed versions, who is at risk, and step-by-step help for WordPress and small business sites.

nexgenheadlines.com

Photos: Wikimedia Commons (credits on each page)