IN PLAIN ENGLISH / 1 MINUTE READ

The short version

On 21 October, serious security flaws were fixed in PHP, the software that runs many WordPress sites. The flaws were not in WordPress itself. The fix needs to be applied by whoever maintains your site's PHP runtime - your host or your own server team. Keeping WordPress up to date alone does not address this issue. If you're unsure what is running or who owns the update, Greycoat can help check and coordinate the fix.

Separately, most vulnerabilities reported in the WordPress ecosystem are found in plugins. Keep only the plugins you need and make sure they are maintained. A different publishing platform can change what you need to look after, but moving platforms does not automatically make a site secure.

Read the detailed analysis

THE DETAILED ANALYSIS

A WordPress site depends on more than WordPress core. Its PHP runtime, host, themes, plugins and accounts each have separate security responsibilities. The October PHP release affected one of those layers; the annual WordPress vulnerability figures describe another. Keeping them separate makes the platform comparison useful.

What happened on 21 October 2026?

The PHP project released fixes for two critical, unauthenticated remote-code-execution vulnerabilities: CVE-2026-109618, involving out-of-memory handling, and CVE-2026-109619, involving stale global state. PHP's advisory says the risk applies to web-facing PHP installations, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It considers the risk highest for mod_php. The supported fixed releases are PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

These are PHP vulnerabilities, not WordPress core vulnerabilities. WordPress.org clarified that no WordPress update addresses these particular flaws. A PHP application may be exposed regardless of whether it uses WordPress. Actual remediation depends on the PHP build and the hosting environment.

How many WordPress ecosystem vulnerabilities were disclosed?

THE ECOSYSTEM IN 2025

Patchstack recorded 11,334 WordPress ecosystem vulnerabilities in 2025, including 1,966 rated high risk for automated attacks.

These are disclosures, not confirmed compromises. Patchstack found 91% in plugins, 9% in themes and 6 low-priority issues in WordPress core.

11,334new vulnerabilities
1,966high-risk vulnerabilities
91%found in plugins

Source: Patchstack's 2026 report, analysing 2025.

Patchstack's database recorded 5,948 new ecosystem entries in 2023, 7,966 in 2024 and 11,334 in 2025. The reporting programme and research attention also changed over that period, so the rising count should not be read as a direct measure of how likely an individual site is to be compromised. A site's installed components and their versions matter more to its immediate exposure.

WordPress ecosystem vulnerability disclosures, 2023 to 2025 Annual disclosures recorded by Patchstack: 5,948 in 2023, 7,966 in 2024, and 11,334 in 2025. The vertical axis starts at zero and ends at 12,000. 12,0009,0006,0003,0000 5,9487,96611,334 202320242025
WordPress ecosystem disclosures, 2023 to 2025. Sources: Patchstack's 2024, 2025 and 2026 reports. Axis: 0 to 12,000. Disclosures are not confirmed attacks.

Treat plugins as production dependencies: keep an inventory, remove unused or unsupported components, monitor advisories, test fixes promptly and verify backups. Patchstack found that 46% of vulnerabilities disclosed in 2025 had no developer fix at disclosure. In the heavily targeted subset it observed, the activity-weighted median time from disclosure to first exploit attempt was five hours. Affected sites may need targeted virtual patching or WAF rules while awaiting a vendor fix, or may need to disable the component. Do not assume a generic host WAF covers a WordPress-specific flaw: in Patchstack's own tests, hosts blocked only 26% of the exploit attempts it ran. Patchstack sells virtual patching, and its test result is not a universal measure of WAF effectiveness. These measures require testing and are not a substitute for a fix.

What does attack activity look like?

Wordfence reported 9.1 billion WAF attacks blocked, 13.8 billion brute-force attempts blocked and approximately 467,000 sites with malware in its Q4 2025 telemetry. Blocked requests are not unique attackers; brute-force attempts are not necessarily attempts to exploit a disclosed software vulnerability; and the malware figure does not identify which vulnerability, if any, was used. These measures cannot be added to Patchstack's disclosure count.

Patchstack's separate exploit telemetry found broken access control to be its most exploited vulnerability category in 2025. It also found older unpatched components among the most targeted. Those observations describe the activity visible to Patchstack, not every WordPress site.

Managed WordPress: less toil, shared responsibility

Managed hosting can take on runtime maintenance, but the precise division of work depends on the plan. IONOS, for example, says automatic updates are enabled by default for WordPress, themes, plugins and the PHP version in its WordPress hosting products. That describes a default setting; it does not establish when a particular server received this security release. Check the site's PHP build and ask the provider what was patched and when.

The site owner still needs to decide which plugins and accounts are necessary, check that backups can be restored and test important site functions after updates. The host can confirm the controls it operates. During a critical release, record the runtime version or vendor backport, the host's confirmation and the outcome of a brief site check.

EmDash and Workers: a different security boundary

Cloudflare describes EmDash 1.0 as an open-source CMS built on Astro. Its sandboxed plugins use capability-limited isolation: on Cloudflare, each runs as a Dynamic Worker; on Node.js, EmDash starts the open-source workerd runtime separately to isolate them. This model is not exclusive to Cloudflare, and it can constrain what an extension may access in ways that differ from a conventional WordPress plugin running inside the site's PHP application. The comparison depends on using that sandboxed plugin model, not on assuming every possible extension is isolated.

An EmDash deployment on Workers does not run the affected PHP runtime to serve its CMS pages, so these PHP CVEs do not apply to that serving layer. Runtime patching has not disappeared: Cloudflare maintains the Workers runtime, including V8 and workerd, while the site owner remains responsible for their application code, configuration and dependencies. A Node.js deployment also brings host and Node runtime patching into its own operating model.

Isolation does not establish a comparative breach rate. Cloudflare introduced EmDash on 1 April 2026 and released 1.0 on 28 September 2026, less than a month before this article. Its ecosystem has had less time for public scrutiny than WordPress. Its configuration, dependencies, data services, administrative access and recovery plan still need review. The choice should be based on the site's functions and the team's ability to operate the new stack, not on vulnerability totals from unlike ecosystems.

Comparison: which operating model fits?

  1. Self-managed WordPress: choose it when direct control matters and you can maintain PHP, the server, WordPress and its extensions, with a tested recovery process.
  2. Managed WordPress: choose it when WordPress features matter and you want a provider to operate parts of the stack. Confirm the plan's patching responsibilities and keep the plugin set lean.
  3. EmDash: consider it when its content and sandboxed plugin model fit the site. It can run on Workers or Node.js, with different runtime responsibilities in each case. Test content, URLs, SEO metadata and editorial workflows before committing to a migration.

Security follows the boundaries you operate. Know what runs your code, who can patch it, which extensions share its privileges, and how quickly you can prove that a fix worked.

Considering your options?

Greycoat works on website migrations and platform decisions. If you know someone with a WordPress site who is weighing a move, or wants to harden what they already have, put them in touch. We can compare the options and, where a move makes sense, plan for content, redirects, search visibility and editorial workflows.

Talk to Greycoat