Website owner resource · Security
PHP Vulnerability October 2026: What Website Owners Need to Know
PHP released security updates on October 21, 2026 addressing CVE-2026-109618 and CVE-2026-109619. If your website uses PHP, ask your hosting provider to confirm that the web-serving runtime is patched. Not every website uses PHP, and a complete rebuild is not automatically necessary.
Published · Last reviewed
By AD Web Design & Development · AD Supply NY Corp.
This is an educational summary, not a security audit of your website. PHP published a configuration-dependent follow-up on October 23; ask your host to review the latest official notice as well as the October 21 fixes.
What is a PHP vulnerability? What happened in October 2026?
A PHP vulnerability is a security flaw in PHP that can let an attacker do something the software should prevent. On October 21, 2026, PHP announced two critical vulnerabilities that can allow unauthenticated remote code execution: an attacker may be able to make an affected server execute code. PHP identifies installations serving web requests as at risk, including PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed. Exposure depends on the installed build and configuration; this does not mean every website is vulnerable.
Source: Official PHP notices
What is PHP, and why do websites use it?
PHP is a server-side programming language. Websites use it to generate pages, process forms and work with databases. WordPress uses PHP, as do many other applications. PHP runs on the hosting server, not simply in the visitor's browser.
Source: PHP language overview
What is PHP2Shell?
PHP2Shell is a nickname used in reporting about these PHP remote-code-execution vulnerabilities. It describes the potential for a PHP flaw to lead to attacker-controlled code on a server; it is not a separate PHP product or a diagnosis that your site has been compromised. Use the CVE identifiers and official PHP advisories when speaking with your host.
Source: Official PHP notices
What are CVE-2026-109618 and CVE-2026-109619?
CVE-2026-109618 concerns corruption during out-of-memory handling: cleanup can treat partially initialized request data as valid. CVE-2026-109619 concerns stale global state: request-owned data can outlive its backing memory and be reused by a later request in the same worker. Both can allow remote code execution. The official advisories contain technical details; business owners should ask their hosting provider to verify patch coverage.
Source: Official PHP notices
Which PHP versions include security fixes?
The October 21 fixes are included in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Install the current patched release supported by your application and host, rather than treating these minimum versions as permanently current. Distribution and LTS vendors may backport fixes without matching these upstream version numbers; obtain confirmation from the vendor. PHP 8.1 and older no longer receive routine upstream updates, though PHP supplied limited source backports for these two issues.
Source: Official PHP notices
| PHP branch | Patched release |
|---|---|
| 8.5 | 8.5.12 |
| 8.4 | 8.4.27 |
| 8.3 | 8.3.36 |
| 8.2 | 8.2.35 |
Are WordPress websites affected by the PHP vulnerability?
WordPress runs on PHP, so its hosting runtime must be checked. Updating WordPress themes or plugins does not by itself update the server's PHP runtime. A WordPress website on an affected PHP build may be exposed; one on a patched build is not automatically affected by these two issues. WordPress's recommended hosting requirements are not proof that the two October CVEs are patched. Ask the host to confirm the actual web-serving PHP version and any vendor patches.
Source: WordPress requirements · PHP security fixes
Does every website use PHP?
No. Websites can use static HTML or runtimes based on JavaScript, Python, Ruby, Java and other technologies. A site that does not use PHP is not affected by a PHP runtime flaw simply because it is on the internet. Its other software still needs appropriate maintenance.
Source: Official PHP notices
How can I find out which PHP version my website uses?
Check the PHP section of your hosting control panel, or ask your host for the version and patch status used to serve your website. WordPress Site Health may show server information. A command-line PHP version can differ from the web-serving version. Avoid leaving a public phpinfo page online: it can expose configuration details. A qualified host or developer can check privately.
Source: Official PHP notices
Does HTTPS protect a website from this vulnerability?
No. HTTPS encrypts traffic between a visitor and the website and helps authenticate the connection. It does not patch vulnerabilities in the server runtime. You need both correctly configured HTTPS and appropriately updated software.
Source: Official PHP notices
What should I ask my hosting provider?
Ask: Which PHP build serves my website? Does it include fixes for both CVEs, including vendor backports? Have all relevant workers been restarted? Has application compatibility been checked? Are recoverable backups available, and is there evidence of compromise? Also ask about PHP's October 23 follow-up on session upload progress (CVE-2026-115560): the official notice describes an unusual configuration-dependent issue and recommends a host-managed precaution pending the next regular release. Do not change server settings blindly.
Source: Official PHP notices
Do I need to rebuild my website because of this?
Not automatically. Updating PHP and checking the application is usually the first step. If compromise is suspected, your host or a qualified security specialist should investigate and recover safely. A rebuild may make sense for an unsupported or unmaintainable site, but these announcements alone are not a reason to discard a working website.
Source: Official PHP notices
What should a small business look for in a secure website developer?
Look for clear account ownership, HTTPS configuration, responsible hosting and access management, software update responsibilities, backups and recovery planning, documented support and reliable performance. Ask what the maintenance plan actually includes and who handles a security incident. Avoid claims that a website is impossible to hack, invented certifications or guaranteed rankings.
Source: Official PHP notices
