
What happened?
Introduction
On 21 October 2026, the PHP team released urgent fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Both could let an attacker run harmful code on a server without logging in. The PHP team advises updating immediately. (PHP advisory)
If your WordPress site runs on a DigitalOcean server or droplets, it could be at risk until PHP is updated.
Why it matters
Think of WordPress as a shop and PHP as the worker who handles every customer request. The flaw is in that worker, not in the shop. An attacker could send specially crafted requests that trick the server into running their instructions.
If exploited, the possible results include:
- The site going down or behaving incorrectly
- Unauthorised access to the server
- Exposure of data stored on the server
- Changed files or the server being used for other attacks
These are possible outcomes, not proof that your site has been attacked.
WordPress itself is not broken. This is a PHP issue, so no separate WordPress update is needed to fix it. Keep WordPress, themes and plugins updated anyway. (WordPress announcement)
Which versions are affected
- Fixed: PHP 8.2, 8.3, 8.4 and 8.5 receive the patches.
- Not fixed: PHP 8.1 and earlier are no longer supported and will not get these fixes from the PHP project.
What to do
If a developer or hosting company manages your server, send them these steps. Otherwise, follow them yourself.
- Back up first. Take a DigitalOcean snapshot of your Droplet, plus a recent backup of your WordPress files and database. This gives you a way back if something goes wrong.
- Check your PHP version. In WordPress, go to Tools → Site Health → Info → Server and note the PHP version. If it is 8.1 or older, updating Ubuntu will not solve the problem. You will need to move to a supported version (see below).
- Install the security update. Ubuntu 24.04 uses PHP 8.3 by default, and Ubuntu released its own fix on 21 October 2026 (notice USN-8948-1). Apply the available system updates, and review what will change before confirming. Ubuntu’s version numbers may differ from PHP’s own, so check the Ubuntu notice rather than the version number alone. If you installed PHP from a third-party repository, check that source for the fix instead.
- Restart the PHP service. The update only takes effect once the service your site actually uses (PHP-FPM or Apache) has restarted. Expect a brief interruption.
- Test your site. Check that key pages load, you can log in to the dashboard, and forms or payments work. Then recheck the PHP version in Site Health.
If you cannot confirm that the PHP serving your site has the fix, assume it is still vulnerable and ask your administrator to verify.
If you run PHP 8.1 or older
Plan an upgrade to a supported PHP version. Test your themes and plugins for compatibility first, and keep your backup ready, because older plugins can break on newer PHP.
*You may try to upgrade your ubuntu core accordingly which will upgrade your php version. However you must follow the step by step guide to upgrade ubuntu from version 18 to 20, then to 22, 24 and lastly 26. as you upgrade your ubuntu version, each version will carry a updated php version with the software.

Why act now
Once flaws become public, attackers scan websites automatically. Small sites are targeted too. A site can look normal while still running vulnerable software, so don’t wait for visible problems.
Updating PHP is a key step, but it doesn’t replace regular maintenance of WordPress, plugins, server settings and backups.
References
This is general guidance. Server setups differ, so confirm which PHP installation your site uses before making changes.
