{"id":940,"date":"2026-10-23T12:08:12","date_gmt":"2026-10-23T11:08:12","guid":{"rendered":"https:\/\/www.enbecom.net\/blog\/?p=940"},"modified":"2026-10-23T12:08:12","modified_gmt":"2026-10-23T11:08:12","slug":"critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded","status":"publish","type":"post","link":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/","title":{"rendered":"Critical PHP security vulnerabilities: what happened and how Enbecom responded"},"content":{"rendered":"\n<p>Two critical security vulnerabilities affecting PHP, one of the world&#8217;s most widely used website technologies, have prompted urgent action from hosting providers and website administrators around the world this week.<\/p>\n<p>Following advance warnings on Tuesday 20 October 2026, emergency security updates were released on Wednesday 21 October to address the vulnerabilities, which could potentially allow attackers to gain unauthorised control of vulnerable web servers.<\/p>\n<p>At Enbecom, we responded rapidly to the announcements, applying security updates to our hosting infrastructure and the servers we manage for clients. We also contacted clients to explain the situation, the steps we had taken and whether any further action was required from them.<\/p>\n<h2>What is PHP, and why is it important?<\/h2>\n<p>PHP is a programming language that powers a significant proportion of the world&#8217;s websites. It operates behind the scenes on web servers, handling tasks such as processing forms, communicating with databases, managing user accounts and generating website content.<\/p>\n<p>Many popular website platforms, including WordPress, Drupal and Joomla, rely on PHP to function.<\/p>\n<p>Unlike the software that visitors interact with directly in their web browsers, PHP runs on the server where a website is hosted. This means that keeping PHP secure is generally the responsibility of the hosting provider or whoever manages the server.<\/p>\n<p>As PHP is so widely used, a serious vulnerability within it can potentially affect a huge number of websites, even when the websites themselves have been properly maintained.<\/p>\n<h2>What happened on 21 October 2026?<\/h2>\n<p>On Tuesday 20 October, the PHP security team issued an advance warning about two critical vulnerabilities, both receiving a severity score of 9.2 out of 10.<\/p>\n<p>The vulnerabilities, identified as <strong>CVE-2026-109618<\/strong> and <strong>CVE-2026-109619<\/strong>, could allow an attacker to exploit weaknesses in PHP&#8217;s handling of memory and internal processes.<\/p>\n<p>In certain circumstances, these weaknesses could enable an attacker to execute malicious commands on a vulnerable server remotely, without first needing to log in or know a password.<\/p>\n<p>This type of security flaw is known as a <strong>remote code execution vulnerability<\/strong>. It is particularly serious because a successful attack could potentially allow criminals to access sensitive information, alter website files, install malicious software or interfere with other services on the affected server.<\/p>\n<p>The precise consequences would depend on the server&#8217;s configuration and the permissions available to PHP, but the potential impact is significant.<\/p>\n<p>Importantly, these vulnerabilities are within PHP itself, rather than in a particular website platform or plugin. This means that even a fully updated WordPress website, for example, could be exposed if the PHP software running on its hosting server had not received the necessary security patches.<\/p>\n<p>Security researchers have demonstrated the possibility of exploiting these vulnerabilities, and attempts to exploit them have been reported in the wild.<\/p>\n<p>The UK&#8217;s <a href=\"https:\/\/www.ncsc.gov.uk\/news\/critical-security-issue-affecting-php\">National Cyber Security Centre (NCSC)<\/a> issued an urgent alert encouraging organisations to identify affected systems, apply the available updates and monitor their services for suspicious activity.<\/p>\n<h2>Which PHP versions are affected?<\/h2>\n<p>The vulnerabilities affect PHP installations handling web requests, including installations that were running supported PHP versions before the emergency updates.<\/p>\n<p>The PHP developers released the following patched versions on 21 October:<\/p>\n<ul>\n<li>PHP 8.5.12<\/li>\n<li>PHP 8.4.27<\/li>\n<li>PHP 8.3.36<\/li>\n<li>PHP 8.2.35<\/li>\n<\/ul>\n<p>Anyone running an earlier release within one of these PHP version families should ensure that the relevant security updates have been applied.<\/p>\n<p>Older PHP versions are also affected. PHP 8.1 and earlier are no longer officially supported by the PHP project, although some operating system and commercial software providers supply their own security fixes for older versions.<\/p>\n<p>It is worth noting that some providers incorporate security patches into their existing software packages without changing the main PHP version number. The important thing is to confirm that the relevant security fixes have actually been installed, rather than relying on a version number alone.<\/p>\n<p>PHP 8.2 is also approaching the end of its official security support, which finishes on 31 December 2026. Website owners still relying on PHP 8.2 should therefore begin planning a move to a newer supported version.<\/p>\n<h2>How did Enbecom respond?<\/h2>\n<p>Protecting the security and reliability of our hosting infrastructure is an ongoing priority at Enbecom.<\/p>\n<p><strong>We regularly update the software running on our hosting servers, including PHP, web server software and other important components.<\/strong> On our standard hosting plans, we only offer PHP versions that remain officially supported, and we install security updates regularly as part of our routine server maintenance.<\/p>\n<p>This approach is particularly important when critical security vulnerabilities are discovered, as it allows us to respond quickly without first having to address the complications associated with obsolete or unsupported software.<\/p>\n<p>When news of the PHP vulnerabilities emerged, we immediately began preparing for the security updates.<\/p>\n<p>Some software providers made their patches available slightly ahead of the planned release time on Wednesday 21 October, enabling us to begin installing updates early.<\/p>\n<p><strong>Within a few hours, the necessary patches had been applied across our own hosting servers and the client servers that we fully manage, apart from a small number of exceptions involving infrastructure supplied by third-party providers.<\/strong><\/p>\n<p>Additional server software updates became available during Thursday 22 October and overnight into Friday 23 October. These were also installed, regardless of whether they were directly related to the original PHP vulnerabilities.<\/p>\n<p>Where third-party infrastructure, older software or unusual server configurations have created additional complications, we have worked to address these and communicate any outstanding requirements to the clients concerned.<\/p>\n<p>We have also contacted our clients to explain the vulnerabilities, outline the action we have taken across the different services we provide and advise them of anything they may need to do themselves.<\/p>\n<p>At the time of publication, <strong>we have found no evidence of successful attacks affecting our own services or the client websites that we manage.<\/strong> Nevertheless, we continue to monitor the situation closely, particularly given the high level of attempted exploitation being reported worldwide.<\/p>\n<h2>Why keeping website software updated is so important<\/h2>\n<p>This week&#8217;s events provide a particularly clear reminder of why software updates are essential to website security.<\/p>\n<p>When people think about keeping a website updated, they often think of installing the latest WordPress version, updating plugins or applying updates to their website&#8217;s theme.<\/p>\n<p>These are all very important tasks, but they are only part of the picture.<\/p>\n<p>A website relies on several layers of technology working together. These can include:<\/p>\n<ul>\n<li><strong>Website software:<\/strong> Platforms such as WordPress, Drupal or Joomla, along with their themes, plugins and extensions.<\/li>\n<li><strong>PHP and other programming technologies:<\/strong> Software that processes website requests and makes dynamic websites work.<\/li>\n<li><strong>Web server software:<\/strong> The systems responsible for delivering website content to visitors.<\/li>\n<li><strong>Databases and other supporting services:<\/strong> Software that stores website information and supports its operation.<\/li>\n<li><strong>The server&#8217;s operating system:<\/strong> The underlying software that manages the server and its resources.<\/li>\n<\/ul>\n<p>A vulnerability in any one of these layers can potentially put a website or server at risk, regardless of how carefully the other layers have been maintained.<\/p>\n<p><strong>The PHP vulnerabilities announced this week demonstrate that keeping a website&#8217;s own software up to date is not enough on its own. The surrounding hosting infrastructure must also be maintained and secured.<\/strong><\/p>\n<p>For website owners, this makes it important to understand who is responsible for each part of their website&#8217;s maintenance.<\/p>\n<p>Depending on the hosting and website management arrangements, responsibility might sit with the hosting company, the website developer, an IT support provider or the website owner themselves.<\/p>\n<p>Regular security updates, supported software versions, reliable backups and appropriate monitoring all contribute to a website&#8217;s overall security.<\/p>\n<p>No hosting provider or website owner can guarantee that new vulnerabilities will never be discovered. However, keeping software supported and regularly updated, and responding promptly when security issues arise, can significantly reduce the risk.<\/p>\n<h2>What should website owners do now?<\/h2>\n<p>If your website is hosted and managed by Enbecom, we have already taken action in relation to the services under our management and contacted clients with relevant information and any further steps required.<\/p>\n<p>If your website is hosted elsewhere, or you manage your own server, we strongly recommend checking the situation with your hosting provider or server administrator as soon as possible.<\/p>\n<p>In particular, website owners should:<\/p>\n<ul>\n<li><strong>Check whether their website uses PHP.<\/strong> Not every website does, so some websites will not be directly affected by these vulnerabilities.<\/li>\n<li><strong>Confirm that PHP has been patched.<\/strong> Ask your hosting provider whether the fixes for CVE-2026-109618 and CVE-2026-109619 have been installed.<\/li>\n<li><strong>Use a supported PHP version.<\/strong> We recommend PHP 8.3 or newer, ideally PHP 8.4 or 8.5 where compatible with your website. Remember that a supported version must still have the latest relevant security patches installed.<\/li>\n<li><strong>Keep website software updated.<\/strong> Continue applying updates to WordPress, other website platforms, themes and plugins to protect against separate security vulnerabilities.<\/li>\n<li><strong>Maintain reliable backups.<\/strong> Ensure that recent backups are available and can be restored if required.<\/li>\n<li><strong>Monitor for unusual activity.<\/strong> Unexpected website changes, unfamiliar administrator accounts, suspicious files or unexplained server behaviour should be investigated promptly.<\/li>\n<\/ul>\n<p>If you are unsure whether your hosting provider has taken action, we recommend contacting them directly and asking for confirmation.<\/p>\n<p>If a vulnerable server cannot be updated immediately, the NCSC advises considering temporary protective measures, including taking affected systems offline where necessary until they can be secured.<\/p>\n<p>Remember that owning or registering a domain name does not, in itself, mean you are affected. These vulnerabilities concern servers running PHP, rather than domain registration or ordinary email services.<\/p>\n<h2>Further information<\/h2>\n<p>For further details about the vulnerabilities and the recommended security updates, the following official resources provide useful information:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.php.net\/archive\/2026.php\">PHP official security announcements and updates<\/a> \u2013 details of the emergency releases, affected software and available fixes.<\/li>\n<li><a href=\"https:\/\/www.ncsc.gov.uk\/news\/critical-security-issue-affecting-php\">UK National Cyber Security Centre: Critical security issue affecting PHP<\/a> \u2013 official UK guidance about the vulnerabilities and recommended action.<\/li>\n<li><a href=\"https:\/\/www.php.net\/supported-versions.php\">PHP supported versions<\/a> \u2013 information about which versions of PHP continue to receive security updates.<\/li>\n<\/ul>\n<h2>Our continuing commitment to security<\/h2>\n<p>The discovery of critical vulnerabilities in widely used software is an unfortunate reality of modern technology. What matters is how quickly and effectively those vulnerabilities are addressed.<\/p>\n<p>At Enbecom, our approach is to maintain supported and regularly updated hosting infrastructure, monitor important security developments and act promptly when new threats emerge.<\/p>\n<p>The events of this week highlight why that work is so important, and why website security needs to be considered across the entire hosting environment, rather than just the website itself.<\/p>\n<p>We will continue monitoring developments relating to these PHP vulnerabilities and applying any further updates necessary to protect the services we manage.<\/p>\n<p><strong>Enbecom clients with any questions about these vulnerabilities or the services we provide can get in touch with our support team by submitting a support request through their <a href=\"https:\/\/www.enbecom.net\/login\">Enbecom Account<\/a>.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Two critical security vulnerabilities affecting PHP, one of the world&#8217;s most widely used website technologies, have prompted urgent action from hosting providers and website administrators around the world this week. Following advance warnings on Tuesday 20 October 2026, emergency security updates were released on Wednesday 21 October to address the vulnerabilities, which could potentially allow&hellip; <a class=\"more-link\" href=\"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/\">Continue reading <span class=\"screen-reader-text\">Critical PHP security vulnerabilities: what happened and how Enbecom responded<\/span><\/a><\/p>\n","protected":false},"author":6,"featured_media":941,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-940","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-enbecom-blog","entry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Critical PHP security vulnerabilities: what happened and how Enbecom responded - Enbecom Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Critical PHP security vulnerabilities: what happened and how Enbecom responded - Enbecom Blog\" \/>\n<meta property=\"og:description\" content=\"Two critical security vulnerabilities affecting PHP, one of the world&#8217;s most widely used website technologies, have prompted urgent action from hosting providers and website administrators around the world this week. Following advance warnings on Tuesday 20 October 2026, emergency security updates were released on Wednesday 21 October to address the vulnerabilities, which could potentially allow&hellip; Continue reading Critical PHP security vulnerabilities: what happened and how Enbecom responded\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/\" \/>\n<meta property=\"og:site_name\" content=\"Enbecom Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/enbecom\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-23T11:08:12+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2026\/10\/PHPOct2026.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Enbecom Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@enbecom\" \/>\n<meta name=\"twitter:site\" content=\"@enbecom\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Enbecom Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/\"},\"author\":{\"name\":\"Enbecom Team\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#\\\/schema\\\/person\\\/85fe6260e0a12b43c759c0aede0f6d72\"},\"headline\":\"Critical PHP security vulnerabilities: what happened and how Enbecom responded\",\"datePublished\":\"2026-10-23T11:08:12+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/\"},\"wordCount\":1766,\"publisher\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/PHPOct2026.png\",\"articleSection\":[\"Enbecom Blog\"],\"inLanguage\":\"en-GB\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/\",\"url\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/\",\"name\":\"Critical PHP security vulnerabilities: what happened and how Enbecom responded - Enbecom Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/PHPOct2026.png\",\"datePublished\":\"2026-10-23T11:08:12+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/PHPOct2026.png\",\"contentUrl\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/PHPOct2026.png\",\"width\":1672,\"height\":941},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/2026\\\/10\\\/23\\\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Critical PHP security vulnerabilities: what happened and how Enbecom responded\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/\",\"name\":\"Enbecom Blog\",\"description\":\"All the latest from Enbecom\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#organization\",\"name\":\"Enbecom\",\"url\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/01\\\/ENBECOM-LOGO-150.jpg\",\"contentUrl\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/01\\\/ENBECOM-LOGO-150.jpg\",\"width\":440,\"height\":130,\"caption\":\"Enbecom\"},\"image\":{\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/enbecom\",\"https:\\\/\\\/x.com\\\/enbecom\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.enbecom.net\\\/blog\\\/#\\\/schema\\\/person\\\/85fe6260e0a12b43c759c0aede0f6d72\",\"name\":\"Enbecom Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/87ef5cfeda25d6c6a68f82b9ef9bae41f181b9632368bd68558074e826ef892a?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/87ef5cfeda25d6c6a68f82b9ef9bae41f181b9632368bd68558074e826ef892a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/87ef5cfeda25d6c6a68f82b9ef9bae41f181b9632368bd68558074e826ef892a?s=96&d=mm&r=g\",\"caption\":\"Enbecom Team\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Critical PHP security vulnerabilities: what happened and how Enbecom responded - Enbecom Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/","og_locale":"en_GB","og_type":"article","og_title":"Critical PHP security vulnerabilities: what happened and how Enbecom responded - Enbecom Blog","og_description":"Two critical security vulnerabilities affecting PHP, one of the world&#8217;s most widely used website technologies, have prompted urgent action from hosting providers and website administrators around the world this week. Following advance warnings on Tuesday 20 October 2026, emergency security updates were released on Wednesday 21 October to address the vulnerabilities, which could potentially allow&hellip; Continue reading Critical PHP security vulnerabilities: what happened and how Enbecom responded","og_url":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/","og_site_name":"Enbecom Blog","article_publisher":"https:\/\/www.facebook.com\/enbecom","article_published_time":"2026-10-23T11:08:12+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2026\/10\/PHPOct2026.png","type":"image\/png"}],"author":"Enbecom Team","twitter_card":"summary_large_image","twitter_creator":"@enbecom","twitter_site":"@enbecom","twitter_misc":{"Written by":"Enbecom Team","Estimated reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#article","isPartOf":{"@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/"},"author":{"name":"Enbecom Team","@id":"https:\/\/www.enbecom.net\/blog\/#\/schema\/person\/85fe6260e0a12b43c759c0aede0f6d72"},"headline":"Critical PHP security vulnerabilities: what happened and how Enbecom responded","datePublished":"2026-10-23T11:08:12+00:00","mainEntityOfPage":{"@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/"},"wordCount":1766,"publisher":{"@id":"https:\/\/www.enbecom.net\/blog\/#organization"},"image":{"@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#primaryimage"},"thumbnailUrl":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2026\/10\/PHPOct2026.png","articleSection":["Enbecom Blog"],"inLanguage":"en-GB"},{"@type":"WebPage","@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/","url":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/","name":"Critical PHP security vulnerabilities: what happened and how Enbecom responded - Enbecom Blog","isPartOf":{"@id":"https:\/\/www.enbecom.net\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#primaryimage"},"image":{"@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#primaryimage"},"thumbnailUrl":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2026\/10\/PHPOct2026.png","datePublished":"2026-10-23T11:08:12+00:00","breadcrumb":{"@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#primaryimage","url":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2026\/10\/PHPOct2026.png","contentUrl":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2026\/10\/PHPOct2026.png","width":1672,"height":941},{"@type":"BreadcrumbList","@id":"https:\/\/www.enbecom.net\/blog\/2026\/10\/23\/critical-php-security-vulnerabilities-what-happened-and-how-enbecom-responded\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.enbecom.net\/blog\/"},{"@type":"ListItem","position":2,"name":"Critical PHP security vulnerabilities: what happened and how Enbecom responded"}]},{"@type":"WebSite","@id":"https:\/\/www.enbecom.net\/blog\/#website","url":"https:\/\/www.enbecom.net\/blog\/","name":"Enbecom Blog","description":"All the latest from Enbecom","publisher":{"@id":"https:\/\/www.enbecom.net\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.enbecom.net\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/www.enbecom.net\/blog\/#organization","name":"Enbecom","url":"https:\/\/www.enbecom.net\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.enbecom.net\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2023\/01\/ENBECOM-LOGO-150.jpg","contentUrl":"https:\/\/www.enbecom.net\/blog\/wp-content\/uploads\/2023\/01\/ENBECOM-LOGO-150.jpg","width":440,"height":130,"caption":"Enbecom"},"image":{"@id":"https:\/\/www.enbecom.net\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/enbecom","https:\/\/x.com\/enbecom"]},{"@type":"Person","@id":"https:\/\/www.enbecom.net\/blog\/#\/schema\/person\/85fe6260e0a12b43c759c0aede0f6d72","name":"Enbecom Team","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/87ef5cfeda25d6c6a68f82b9ef9bae41f181b9632368bd68558074e826ef892a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/87ef5cfeda25d6c6a68f82b9ef9bae41f181b9632368bd68558074e826ef892a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/87ef5cfeda25d6c6a68f82b9ef9bae41f181b9632368bd68558074e826ef892a?s=96&d=mm&r=g","caption":"Enbecom Team"}}]}},"_links":{"self":[{"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/posts\/940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/comments?post=940"}],"version-history":[{"count":1,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/posts\/940\/revisions"}],"predecessor-version":[{"id":942,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/posts\/940\/revisions\/942"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/media\/941"}],"wp:attachment":[{"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/media?parent=940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/categories?post=940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.enbecom.net\/blog\/wp-json\/wp\/v2\/tags?post=940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}