Emergency Security Update for WordPress Websites: Early Attacks Reported

21 October 2026 · 3 min read

Which websites are affected?

The flaw is in PHP, the software that runs underneath websites built on WordPress, WooCommerce, Joomla, Drupal and Magento, along with many custom sites and client portals.

It can’t be fixed by updating WordPress or plugins. The fix is applied on the server where the website is hosted. Your website developer, or the provider that built your site, will know how your site is set up and who needs to apply it.

What is the risk?

There are two flaws, tracked as CVE-2026-109618 and CVE-2026-109619, both rated critical (9.2 out of 10) in PHP’s official security advisory. They could let someone on the internet take control of a vulnerable website without needing a password.

If that happened, an attacker could:

  • Change your website or redirect visitors elsewhere
  • Read enquiries, client portal data or customer details stored on the site
  • Steal payment details from online checkouts
  • Use your server to send spam or attack others

If your site holds client information, a compromise could become a notifiable data breach under the Privacy Act.

Is it being exploited?

Early attacks have been reported. Cloudflare and several hosting companies have seen attackers starting to target the flaws, and PHP’s advisory notes that a working attack has been demonstrated. Attacks typically increase now that the fix is published, as attackers look for sites that haven’t been updated.

Cloudflare has added temporary protection for websites that use its web application firewall (WAF), a security filter that sits in front of your website. This reduces the risk but is not a substitute for the update.

Who is most at risk?

The update has been released for the supported versions: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

Websites on PHP 8.1 or older don’t receive official updates. Some hosting companies can apply a temporary backported fix, but the reliable solution is upgrading. We recommend PHP 8.3 or later, as PHP 8.2 reaches end of life in December 2026.

What to do this week

1. Contact your website developer. Email your website developer, or the provider that built your site, and copy and paste these questions:

  • Which version of PHP is our website running?
  • Is the PHP security update released on 22 October 2026 (version 8.2.35, 8.3.36, 8.4.27 or 8.5.12) installed?
  • If we’re on PHP 8.1 or older, what is the plan and timeframe to upgrade?
  • Is our website protected by a web application firewall (such as Cloudflare), and is it set up so the website can only be reached through it?
  • Do we have a recent backup stored separately from the website?

2. If it can’t be updated within 24 hours, take it offline. If the update can’t be installed within 24 hours, or your site needs an upgrade first, ask your website developer to replace the website with a simple holding page until it’s fixed. The holding page must be a plain HTML page, not a WordPress “maintenance mode” plugin, which doesn’t protect you. A few days of a basic page with your contact details is far less disruptive than a compromised website.

3. Assign clear accountability. Your website should have a designated owner responsible for its ongoing maintenance and security. This is typically formalised in a service agreement with your website developer, or managed in-house where the appropriate skills exist.

Unsure what your website runs on, or need advice? Contact our Technical Assistance Centre or call 1300 14 10 10.

Ready to take the next step?

Book a technology assessment and find out how techosity can help your business.

Book Your Technology Assessment
Call us on 1300 14 10 10