What the recent advisories mean
On 21 October, PHP issued fixes for CVE-2026-109618 and CVE-2026-109619, two critical vulnerabilities that can enable remote code execution without authentication on affected servers. WordPress and other PHP-based applications may be exposed through their hosting runtime. Read ENISA’s joint statement ↗
PHP lists 8.5.12, 8.4.27, 8.3.36 and 8.2.35 as fixed releases for those two issues. Hosting vendors may supply backported fixes; a version label alone does not prove patch status. Check PHP’s official advisory ↗
A 23 October follow-up describes a separate, unusual session-configuration issue, CVE-2026-115560, with temporary guidance pending its regular release. Ask your host to review this too. Read the follow-up ↗
These are PHP runtime issues, not evidence that every WordPress site is compromised. Updating WordPress or installing a security plugin is not the same as patching PHP. Some managed hosting platforms have already protected their customers; confirm with your own provider. WordPress.com’s hosting guidance ↗