WordPress Is Updated — But Is Your Hosting PHP Patched?

Tom — Singapore Digital Business & Systems Consultant

Tom

Digital Business & Systems Consultant · Singapore

6 min read Article date First published
WordPress Is Updated — But Is Your Hosting PHP Patched?

Not necessarily. An updated WordPress dashboard does not mean your hosting PHP is patched. WordPress, plugins and themes are updated inside your website; PHP, the engine that runs them, is updated on the server, usually by your host. Here is who looks after each layer, and what record shows the work was done.

Lessons from the October 2026 PHP security updates. A reference guide written afterwards; sources checked 31 October 2026.

Key takeaways

  • Website and server updates are separate; one does not trigger the other.
  • One hosting account can run different PHP versions per domain, so check each site.
  • Ask for evidence per layer: versions before and after, the date and who did it.
  • A patch closes known flaws from that day on. It does not prove there was no earlier break-in.

What the October 2026 updates showed

On 21 October 2026, PHP released emergency fixes for two critical flaws in PHP itself (CVE-2026-109618 and CVE-2026-109619), nicknamed "PHP2Shell" by some security publishers. PHP said they could be triggered before any website code runs, and that only an update was a complete fix (PHP: News Archive 2026). Updating WordPress could not close them.

The October incident in detail, with a sample request for your host.

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

The layers under your website

WordPress core, plugins and themes

The layer you can see. You, your developer or a maintenance provider applies these updates, and the website security basics still apply. They only change files inside your website.

The PHP runtime

PHP is installed on the server, not in your website folder. On shared hosting the provider patches it; you may only choose which installed version your domain uses, and the host can disable or limit that option (cPanel: MultiPHP Manager). On a VPS, the server's administrator is responsible.

That split is why the check belongs with your host. CNA's report on the PHP patching warning for Singapore organisations reports Singapore's Commissioner of Cybersecurity warning that many organisations, especially SMEs relying on external IT vendors or hosting providers, may not realise their systems are vulnerable, and advising anyone unsure to contact their IT team, developer or host. For the technical detail, see CSA's PHP2Shell alert and PHP's own advisories.

Version numbers need care. PHP said Linux distributions and long-term support vendors received the October patches in advance, and a vendor may backport fixes without changing the upstream version, so judge by the vendor's package record.

Web server and system dependencies

Alongside PHP sit the web server (Apache, LiteSpeed or Nginx), the operating system's libraries and the database server, usually the host's job. PHP's October notice covered all PHP installations serving web requests, including PHP-FPM, Apache with mod_php and LiteSpeed. After a PHP update, ask the host to confirm the PHP service was restarted to load the new build.

One account, several PHP versions

In cPanel, each domain can use any installed PHP version or inherit the server-wide default, and each version has its own configuration file (cPanel: About PHP). So "PHP 8.3 has been updated" covers domains on 8.3, not an old microsite on an earlier version. Ask for the version used by every domain and subdomain.

Scheduled jobs and development machines

Scheduled jobs (cron) run backups, reminder emails and similar tasks. cPanel installs a separate command-line PHP binary for each version, and a job can call one directly. Ask which binary each job uses and whether that build is patched.

List every copy of the site: public staging sites, old copies in a subfolder, and developer machines holding your site or database. Patch each copy, or remove it.

Who checks what: a responsibility table

LayerUsually done byEvidence to ask forOwner keeps
WordPress, plugins, themesDeveloper or maintenance providerOld and new versions, date, key pages and forms testedUpdate log
PHP, per domainHost, or VPS administratorVersion and package per domain, date, any backport noteDomain and PHP version list
Web server and system packagesHost or server administratorPatched packages installed and PHP service restartedDated confirmation
Scheduled jobsDeveloper; host confirms the binaryEach job and the PHP binary it callsJob list
Staging, old copies, developer machinesDeveloperEach copy's PHP version, or its removalCopy inventory
Business checkOwner and developerKey pages, enquiry form, checkout and admin login testedDated sign-off

A maintenance agreement should name who checks each layer. Ask at your next review:

  • Which layers does our agreement cover, by name?
  • Who watches PHP security announcements, and how will I hear about updates?
  • Which PHP version and build does each of my domains use?
  • Where is the update log, and can I see it?

A fictional example: two domains, one assumption

(Fictional example) Harbour Kitchen Supplies has a WordPress shop at example.com.sg and a booking page on a second domain, in one cPanel account. After the October news, the developer updated WordPress and every plugin: "all updated". The owner asked which PHP version each domain used.

The shop was on a patched build. The booking page, set up by a former freelancer, was on an older version the PHP project no longer supports. Moving it took a compatibility test and about half a day of developer time (see how to plan a PHP upgrade). A nightly stock-sync job calling PHP directly joined the list. The result: a dated record of what runs where, not proof of what happened before.

Keep the evidence, and know its limits

File each confirmation with the date, versions before and after, and who did the work. But a patch does not prove the site was never compromised earlier. PHP noted that an absence of errors in logs is not proof of safety, and a clean malware scan is not a forensic guarantee. A suspected break-in needs its own investigation.

Check the patch record for your actual site

Not sure who updates your PHP? Get in touch and I will review what your maintenance arrangement covers and what the patch record shows for the actual site. If it needs a newer PHP version and compatibility work, a website revamp may follow, scoped after the review. A review shows what is covered and what is not; it cannot promise a site is secure.

Sources (checked 31 October 2026)

Frequently Asked Questions

Does updating WordPress update PHP?

No. WordPress updates change files inside your website. PHP is installed on the server and updated by your host or server administrator, so it needs its own check and record.

Can two sites on the same server use different PHP versions?

Yes. In cPanel, each domain can use any installed PHP version or inherit the server default, so check each domain, not just the account.

Can a cron job use a different PHP binary from the website?

It can, depending on how the job was set up: cPanel provides a separate command-line binary for each PHP version. Ask your host or developer which binary each job uses and whether it is patched.

What if the provider says it backported the fix?

That can be legitimate, as some vendors add security fixes to an older-numbered package. Ask for the package name and the vendor advisory or changelog entry listing the fix, and file it.

Who should watch for PHP security announcements?

Whoever manages the server: usually the host on shared hosting, or the VPS administrator. Your maintenance agreement should name them and say how you will hear about updates.

Not sure who patches PHP for your website? Let me review your maintenance coverage and the patch record for the actual site.

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

Contact