Skip to content
Antoine Le LouëtIndependent senior developer (Home)
Back to the Journal

News4 min read

PHP vulnerabilities of 21 October 2026: is my site affected, and how can I protect it?

Two critical vulnerabilities affect PHP. Check your site, isolate vulnerable services if needed and apply the fixes released on 21 October 2026.

A barrier blocks public access to the vulnerable PHP service; after patching and verification, access can be restored.
If the fix cannot be applied immediately, isolating the exposed service allows you to wait for its update. Conceptual diagram.

What is happening with PHP today?

On 21 October 2026, fixes were released for two critical PHP vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619, also called PHP2Shell. Under certain conditions, someone without an account can cause code to execute on the server. CERT-FR confirms the remote code execution risk in its alert of the day.

PHP is the software that executes code for many websites on their servers. The visitor's browser then receives the page produced. A vulnerability at that level can therefore affect a site whose owner has changed nothing recently. For a business, the concern is protecting the application and data the server can access.

This news update reflects information available on 21 October 2026. Fixes are available: they now need to be deployed rather than waiting for another release.

WordPress or an online shop: how do I know whether my site is affected?

If your site uses WordPress, start by checking its PHP version under Tools > Site Health > Info > Server, or in your hosting panel. WordPress explains that these vulnerabilities affect PHP and that no WordPress update is planned to fix them. Updating only the CMS or its plugins therefore does not replace the server patch.

For another website or business application, ask the technical owner whether PHP handles web requests. Also consider subdomains, older applications and test environments accessible from the internet. I recommend recording each service's host and the person responsible for applying the fix.

A site that does not use PHP is not directly exposed to these two vulnerabilities. Its appearance cannot tell you: the hosting inventory provides the answer.

Should PHP servers be disabled while waiting?

If a vulnerable PHP service is accessible from the internet and cannot be patched immediately, have its public access temporarily disabled. CERT-EU recommends considering this isolation until the fix is applied and verified. With managed hosting, request this intervention from the provider.

I recommend blocking traffic to the application at the web server or proxy, or stopping the affected PHP service if that suits the hosting setup. A maintenance page must be served without executing vulnerable PHP. A simple maintenance screen generated by the CMS may still let requests reach the PHP engine.

Internet access is closed before PHP while patching takes place. It is reopened after checking the patched service.
Isolation must act before PHP execution. A maintenance message displayed by the application does not prove that isolation.

Have other access paths checked, including the server's direct address behind a proxy. Shutdown means a service interruption: prepare a message for users and a contact method. Bringing the service back online must follow patch verification.

Which PHP versions should be installed?

PHP publishes patched versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12 for the corresponding branches. Ask your host which version is actually running and for confirmation that both CVEs are fixed. For an older branch, have them check for a maintainer-provided patch and prepare migration to a supported version.

A Linux distribution can incorporate the fix into its own package without displaying PHP's published version number. Ubuntu's bulletin of 21 October, for example, lists patched packages with specific numbering. The check must therefore use the vendor security advisory and full package version.

  1. Identify all affected services and retain the information needed for the intervention.
  2. Install the patched package or image, then restart or replace the processes running PHP.
  3. Check the version actually used by the site, then test essential journeys such as login or an order.
  4. Restore public access after those checks and monitor errors and security events.

Is updating enough if the site has already been attacked?

On 21 October, Cloudflare reports observing attack traffic targeting these vulnerabilities. That justifies prompt action; it does not prove your own site was compromised. A web application firewall may help during the intervention but does not remove the need to update PHP.

I recommend preserving logs before rotation. If you discover unknown files, added accounts or unusual activity, request incident analysis. The patch closes a vulnerability; it does not automatically remove access an attacker may already have installed.

Send this to your host: 'Please confirm whether our site is exposed to CVE-2026-109618 and CVE-2026-109619, isolate it if immediate patching is impossible, then tell us which patched package was deployed and the results of the checks.'

Sources and useful links

Share on LinkedIn (new tab)

Keep reading
All articles in this category