PHP2Shell Explained: What Singapore Website Owners Should Ask Their Hosting Provider

Tom — Singapore Digital Business & Systems Consultant

Tom

Digital Business & Systems Consultant · Singapore

7 min read Article date First published
PHP2Shell Explained: What Singapore Website Owners Should Ask Their Hosting Provider

PHP2Shell is a nickname for two critical flaws in PHP, the language behind WordPress and many custom websites, fixed in emergency releases on 21 October 2026. Because the flaws are in PHP itself, updating WordPress or plugins does not fix them; updating PHP does. Ask your hosting provider to confirm, for each domain, which PHP build serves your site, that it includes both fixes and was restarted, and that key functions still work.

Retrospective: PHP security releases, 21 October 2026; follow-up, 23 October.

Key takeaways

  • "PHP2Shell" is a nickname used by security researchers, not an official PHP name, for CVE-2026-109618 and CVE-2026-109619.
  • The flaws are in PHP itself, so WordPress and plugin updates do not fix them; updating PHP does.
  • 8.2.35, 8.3.36, 8.4.27 and 8.5.12 were the first fixed releases: minimums, not "the latest version".
  • Get written evidence per domain, then test your key business functions.
  • A patch, clean scan or clean log does not prove the site was never compromised.

What PHP2Shell is, in plain language

Each time someone opens a page on a PHP website, the server runs PHP to build it. PHP said these flaws can allow unauthenticated remote code execution: a stranger with no login could potentially run their own code on the server. Both official advisories rate them Critical:

  • CVE-2026-109618 ("RCE via OOM corruption"): PHP's out-of-memory handling can interrupt PHP while internal request data is only partly initialised.
  • CVE-2026-109619 ("RCE via stale global state"): internal state owned by a request can survive after the memory behind it has been freed.

PHP's announcement says the attack can be triggered before any application code runs, so this is not a WordPress plugin bug. It covers PHP serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. "PHP2Shell" does not appear in PHP's own advisories.

CNA's report on worldwide PHP website shutdowns describes agencies and companies taking sites offline on 21 October, and CNA's report on the PHP patching warning for Singapore organisations quotes Singapore's Commissioner of Cybersecurity: "do not wait". For what to patch, rely on PHP's advisories and CSA's PHP2Shell alert.

Who maintains PHP for your website

The usual split; your hosting plan or maintenance agreement confirms it:

LayerUsually looked after byEvidence to ask for
PHP runtime and packagesHost (shared or managed hosting) or server administrator (VPS or cloud)Fixed build installed, PHP restarted
PHP version per domainHost or developerEach domain on a patched build
WordPress, plugins, themesDeveloper or maintenance providerUpdates and compatibility tested
Records and sign-offYou, the ownerReplies and check results kept

On cPanel hosting, for example, each domain can use its own PHP version and each installed version has its own php.ini file, so a screenshot of the default version is not a full inventory. More on this split: WordPress updates versus hosting PHP.

First fixed versions (21 October 2026)

The first upstream PHP releases containing both fixes:

PHP branchFirst fixed release
8.28.2.35
8.38.3.36
8.48.4.27
8.58.5.12
8.1 and olderEnd of life; minimal source backports only; ask your vendor

These are historical minimums for these two CVEs, not "the latest version"; ask for the provider's current security build.

PHP says Linux distributions and long-term-support vendors received the patches in advance, so a vendor package may carry the fixes under an older-looking label. Separately, PHP 8.2's upstream security support ends on 31 December 2026: see planning a PHP 8.2 upgrade.

Ask for evidence per domain

"We've patched the server" is a start, not evidence. A written request like this gets specifics.

Sample request to your hosting provider

Sample text to adapt — not sent by us. Replace the fictional domains with yours.

Subject: PHP security update evidence for example.com.sg

Hello, for each domain, subdomain and staging copy on our account (including example.com.sg and shop.example.com.sg), please confirm:

  1. 1The PHP version, build and handler (such as PHP-FPM or LiteSpeed) actually serving it today, not just the server default.
  2. 2That this build includes the fixes for CVE-2026-109618 and CVE-2026-109619, with the vendor advisory or changelog reference if they were backported.
  3. 3Whether any later PHP advisory applies to us, including CVE-2026-115560 (23 October 2026), and what you have done.
  4. 4When PHP services and worker processes were restarted after the update.
  5. 5Which PHP build our cron jobs and command-line scripts use, and whether it was updated.
  6. 6Whether any temporary workaround replaced an update, and when the full update went in.

We will then check our homepage, enquiry form, checkout, scheduled jobs and admin login. Thank you.

Patch in stages, then check key functions

Confirm a recent backup, update a staging copy first where one exists, update live in a quiet window, confirm PHP restarted, then run these checks. On shared hosting, leave PHP settings to the provider; tweaking them is no substitute for updating.

  • Homepage and key pages load on phone and desktop.
  • A test enquiry from each form reaches the inbox staff actually read.
  • Checkout, if you sell online: a supported test order, with its order record and confirmation email.
  • Scheduled jobs: the next backup, reminder email or report actually ran.
  • Admin login works and a small draft change saves.
  • Any new PHP errors since the update were reviewed.

A loading homepage is not a full acceptance check; forms and scheduled jobs can fail quietly. For the wider habits, see website security basics.

A separate PHP notice on 23 October 2026

PHP's informational advisory on session upload progress is separate from PHP2Shell. It names CVE-2026-115560 and concerns an unusual set-up: an application that switches PHP's session serialisation handler at runtime before the session starts. PHP suggested setting session.upload_progress.enabled to 0 until its next regular bugfix release; applications that never change the handler at runtime can keep the feature on.

As of 31 October 2026, no full advisory, fixed version or severity score had been published. Ask your host and developer whether it applies rather than changing settings yourself.

Administrator note: PHP's 26 October Windows rebuilds (such as 8.4.27-1) fix a separate Brotli issue, CVE-2026-111497.

What to keep on file afterwards

  • The provider's written reply: domains, builds, handler, update and restart times, and any vendor advisory for backported fixes.
  • Your check results: date, who checked, what failed and how it was fixed.
  • The host's answer on the 23 October advisory.
  • Who handles the next PHP update, and when you next review it.

A patch closes the hole from installation onwards; it does not prove nothing happened before. PHP notes that a clean log is not proof of safety.

Unknown admin users, unexpected redirects or spam from your domain call for a separate investigation by someone qualified.

A fictional example

(Fictional example) Lay Hoon's aircon servicing firm runs WordPress, with a booking form on a subdomain. Her developer had updated WordPress and the plugins. Using the sample request, she learned the main site ran a vendor PHP package with both fixes backported, but the booking subdomain was still on an older, unsupported PHP version. After the developer's staging test and one small email fix, the host moved it to a supported, patched build. It took a week of emails and two short checks. The records cannot prove nothing happened earlier, but she now knows who patches what.

Need help reading the evidence?

If your provider's reply is hard to interpret, I can review the patch evidence with you and check your forms, checkout, scheduled jobs and admin access. It is a review, not a forensic investigation, and cannot certify that a site was never compromised. Contact me with your domain list and the provider's reply, or see web and email solutions if hosting is part of a wider domain, email and website review.

Sources (checked 31 October 2026)

Frequently Asked Questions

Is PHP2Shell a WordPress plugin problem?

No. The flaws are in PHP itself, and PHP says the attack can be triggered before any application code runs. WordPress and plugin updates do not install a fixed PHP build.

Does a security plugin replace PHP patching?

No. PHP says only an update is a complete solution; other measures reduce some attack paths but do not make an installation safe. Treat a plugin or firewall as an extra layer.

Is an older version label always unpatched?

Not necessarily. Linux distributions and other vendors may backport fixes under their own version labels, so ask for the vendor's advisory or changelog.

Does patching prove the website was never compromised?

No. A patch only closes the vulnerability from the time it is installed. A clean log or malware scan is not a forensic guarantee either.

Is the 23 October advisory part of PHP2Shell?

No. It is a separate notice naming CVE-2026-115560, about an unusual session configuration. As of 31 October 2026 it had an interim mitigation but no full advisory or fixed version.

Not sure your hosting provider's reply covers everything? I can review the PHP patch evidence and check your website's essential functions with you.

No obligation. No sales pitch. Just an honest conversation.

お問い合わせ