Nexcess outage history

We are aware of recent reports regarding two critical vulnerabilities affecting PHP, identified as CVE-2026-109618 and CVE-2026-109619. These vulnerabilities may affect web servers running PHP 5.4 and later and could potentially allow remote code execution. Our Security and Engineering teams are actively reviewing our hosting environments to assess potential impact. As a precautionary measure, we are implementing appropriate mitigations and working to deploy the necessary security updates across affected systems as they become available. We are continuing to closely monitor the situation and will provide further updates as additional information becomes available. If you need assistance or have any concerns, please contact our Support team.

Our Security and Engineering teams are continuing to evaluate the optimal patching strategy for our hosting environments. We are currently analyzing the security releases and testing deployment paths in our staging environments to ensure service stability. At this time, no patches or modifications have been rolled out to production systems. Our infrastructure remains under heightened monitoring, and we will share further details here as soon as our deployment plan and maintenance windows are finalized. If you need assistance or have any concerns, please contact our Support team.

Our Engineering teams are continuing to deploy and verify patched PHP builds across our hosting environments. The rollout is progressing, and teams are checking that the appropriate update is applied for each environment. The fixed PHP versions identified so far include: PHP 8.x: 8.0.30-11, 8.0.30-12, 8.0.30-21, 8.1.34-4, 8.1.34-5, 8.1.34-6, 8.2.34-2, 8.2.35, 8.3.35-2, 8.3.36, 8.4.26-2, 8.4.27, 8.5.11-2, and 8.5.12 PHP 7.x: 7.0.33-3, 7.0.33-29, 7.1.33-3, 7.1.33-20, 7.2.34-2, 7.2.34-12, 7.3.31-2, 7.3.33-15, 7.4.33-18, 7.4.33-19, and 7.4.33-31 PHP 5.x: 5.2.17-3, 5.2.17-27, 5.3.24-2, 5.3.29-29, 5.4.14-2, 5.4.45-2, 5.4.45-82, 5.5.38-2, 5.5.38-64, 5.6.40-15, and 5.6.40-25 If you would like to check your sites PHP information, please follow the steps in this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file Our infrastructure remains under heightened monitoring as the rollout continues. We will share further updates here as work progresses and additional information becomes available.

Our Security and Engineering teams are continuing to deploy and verify security updates across our hosting environments. The work is progressing in stages, and teams are monitoring systems throughout the rollout to help maintain service stability. We are continuing to assess the remaining environments and will share further updates as patching progresses. To check the PHP version currently running on your site, please follow this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/ If your site is running an unsupported or end-of-life PHP version, we recommend updating your code to a supported version and switching to it as soon as possible. If you need assistance or have concerns, please contact our Support team.

Our Security and Engineering teams continue to assess the remaining hosting environments and verify the deployment of security updates. The rollout is progressing in stages, with teams monitoring systems to help maintain service stability. We will continue to monitor progress and share further updates as more information becomes available. To check the PHP version currently running on your site, please refer to this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/ The fixed PHP versions identified so far include: PHP 8.x: 8.0.30-11, 8.0.30-12, 8.0.30-21, 8.1.34-4, 8.1.34-5, 8.1.34-6, 8.2.34-2, 8.2.35, 8.3.35-2, 8.3.36, 8.4.26-2, 8.4.27, 8.5.11-2, and 8.5.12 PHP 7.x: 7.0.33-3, 7.0.33-29, 7.1.33-3, 7.1.33-20, 7.2.34-2, 7.2.34-12, 7.3.31-2, 7.3.33-15, 7.4.33-18, 7.4.33-19, and 7.4.33-31 PHP 5.x: 5.2.17-3, 5.2.17-27, 5.3.24-2, 5.3.29-29, 5.4.14-2, 5.4.45-2, 5.4.45-82, 5.5.38-2, 5.5.38-64, 5.6.40-15, and 5.6.40-25 If your site is running an unsupported or end-of-life PHP version, we recommend updating your code to a supported version and switching to it as soon as possible. If you need assistance or have any concerns, don't hesitate to get in touch with our Support team.

We are continuing to work on a fix for this issue.

Patch deployment is ongoing across our fleet. We appreciate your continued patience.

Patch deployment continues across the affected hosting environments. Our Security and Engineering teams are monitoring the rollout to ensure successful deployment and maintain service stability. We will continue to provide updates as progress is made. Thank you for your patience.

The Patch deployment is underway across affected environments with good progress. We will share another update as soon as more information is available. Thank you for your understanding and patience.

The security patch deployment is progressing well across the affected environments. Our teams are continuing to work toward completing the deployment and ensuring the security of the impacted services. We will provide further updates as more information becomes available.

Patch deployment is progressing well across the affected environments. To check the PHP version currently running on your site, please refer to this help article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/ The fixed PHP versions identified so far include: PHP 8.x: 8.0.30-11, 8.0.30-12, 8.0.30-21, 8.1.34-4, 8.1.34-5, 8.1.34-6, 8.2.34-2, 8.2.35, 8.3.35-2, 8.3.36, 8.4.26-2, 8.4.27, 8.5.11-2, and 8.5.12 PHP 7.x: 7.0.33-3, 7.0.33-29, 7.1.33-3, 7.1.33-20, 7.2.34-2, 7.2.34-12, 7.3.31-2, 7.3.33-15, 7.4.33-18, 7.4.33-19, and 7.4.33-31 PHP 5.x: 5.2.17-3, 5.2.17-27, 5.3.24-2, 5.3.29-29, 5.4.14-2, 5.4.45-2, 5.4.45-82, 5.5.38-2, 5.5.38-64, 5.6.40-15, and 5.6.40-25 If your site is running an unsupported or end-of-life PHP version, we recommend updating your code to a supported version and switching to it as soon as possible. If you need assistance or have any concerns, don't hesitate to get in touch with our Support team.

Our team has identified a subset of Cloudhost outages in the US-Midwest-2 region and is actively investigating the issue. We will provide another update as soon as more information becomes available. We appreciate your patience as our team works to resolve this issue. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

Our team has confirmed that the affected Cloudhost services in the US-Midwest-2 region are operating normally. We are continuing to monitor the environment to ensure services remain stable. We appreciate your patience while our team worked to resolve the issue.

We have been monitoring the situation, and everything has remained stable. This incident has now been resolved.

WordPress has identified a critical security vulnerability designated as "Click2Shell" affecting all WordPress versions prior to 7.1.1. This vulnerability can enable unauthenticated Remote Code Execution (RCE) when a logged-in administrator visits a specially crafted link. Current Status & Hosting Actions Our engineering team is currently assessing our entire hosting fleet and determining next steps. There are currently no known workarounds for this vulnerability other than upgrading to the latest version of WordPress. Recommended Action for Customers We strongly advise all customers managing WordPress installations to review their environments immediately and update to WordPress version 7.1.1. We will continue to monitor the situation closely and provide further updates as new information becomes available.

Our Engineering team continues to assess and work on the WordPress security vulnerabilities across our hosting fleet. A new critical vulnerability, CVE-2026-87902, has been disclosed. WordPress 7.1.2 includes the security fix for this vulnerability. Recommended Action for Customers We strongly advise all customers managing WordPress installations to update to WordPress version 7.1.2 immediately. We will continue to monitor the situation closely and provide further updates as new information becomes available.

As part of our proactive security efforts, Nexcess System Engineers scanned our fleet and automatically upgraded WordPress installations where possible to the appropriate patched versions. Automated update attempts were unsuccessful for some websites due to site-specific errors. Customers with websites that were unable to be upgraded should receive a ticket identifying the server and path to the website. All customers are strongly encouraged to confirm the Wordpress version for all of the websites, including those in staging or development, have been updated to the latest minor version of Wordpress released on September 22nd in order to protect the website from this exploit. For additional information, please refer to the official WordPress security announcements: https://wordpress.org/news/2026/09/wordpress-7-1-2-release/ https://wordpress.org/documentation/wordpress-version/version-7-1-2/ If you have any questions or need assistance with the update process, please contact our Support team. You can reach us through the following channels: Live Chat via the Customer Portal: https://my.nexcess.net/ Email: [email protected] We appreciate your patience and understanding as we work to secure your services.

We are currently aware of an issue affecting a third-party platform used by our Support teams to manage and respond to client cases. The provider is actively investigating the issue and working toward a resolution. As a result, clients may experience delays in responses to support cases while the issue is ongoing. Our teams are monitoring the situation and will continue responding to cases as quickly as possible. We will provide further updates as more information becomes available.

The issue affecting the third-party platform used by our Support teams has been resolved. The provider has confirmed that service stability and performance have returned to expected levels, and our teams are no longer seeing ongoing impact. Support case access and case management functionality have returned to normal. We apologize for the disruption and any delays this may have caused.

We are currently investigating a performance issue affecting a subset of our cloudhosts, cloudhost-4892688.us-midwest-2.nxcli.net and cloudhost-4892180.us-midwest-2.nxcli.net, in the US-Midwest-2 region. Customers may experience slowness or degraded performance, and there is a potential for service interruption while the issue is being investigated. Our systems engineers have been engaged and are working to identify the cause and restore normal performance as quickly as possible. We appreciate your patience. If you have any questions or concerns, please contact us via live chat or case.

Our engineers have successfully recovered the impacted cloudhosts. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed

This incident has been resolved.

Our Engineers are investigating an interruption in service affecting cloudhost-9412708-us-midwest-1-nxcli-net and cloudhost-10309510.us-midwest-1.nxcli.net. We understand the inconvenience this may cause and truly appreciate your patience while we resolve the issue. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

The issue has been identified, and our teams are actively working toward a resolution. We will provide further updates as more information becomes available. Thank you for your patience.

Our engineers have successfully recovered the service on the impacted cloudhost. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

This incident has been resolved.

We are aware of recent reports regarding a critical, unpatched zero-day vulnerability, commonly referred to as “StyleSmuggler”, affecting Magento and Adobe Commerce. At this time, our teams are actively reviewing server environments to assess any potential impact. As a precautionary measure, our Security team is implementing the appropriate mitigations while we continue our investigation and monitor for further guidance. We will provide further updates as more information becomes available. If you need assistance or have any concerns, please contact our Support team .

As part of our ongoing mitigation efforts, we have implemented additional security protections across affected Magento/Adobe Commerce environments. This includes a full block on GraphQL requests to help reduce the risk of unauthorized code execution. Customers using headless/PWA storefronts or applications that rely heavily on GraphQL may experience some impact from these protections. At this time, there is no official vendor patch available. We recommend continuing to monitor your site for unusual activity or unexpected changes and contacting Support if you notice any issues with your storefront or suspect your site may have been compromised. We will provide further updates once an official security patch becomes available. Our teams are continuing to monitor the affected environments and the effectiveness of these mitigations. We will continue to assess the situation and provide additional updates as new information becomes available.

Our security teams are actively scanning affected environments for indicators of compromise. Initial scanning has identified potential findings that are currently being reviewed and validated. We are continuing to enhance our scanning capabilities to provide additional visibility into potential compromises. We are also reviewing affected Magento environments and developing remediation guidance for confirmed cases. Customers may experience some impact if their storefront or applications rely heavily on GraphQL, including headless/PWA implementations. We recommend continuing to monitor your environment for unusual activity or unexpected changes and contacting Support if you observe any issues or suspect your site may have been compromised. Our teams will continue to monitor the situation closely and provide further updates as additional information becomes available.

Our teams remain actively engaged and are continuing to investigate the Magento vulnerability and its potential impact. Security and Engineering are working closely to validate findings, expand scanning, and provide clear remediation guidance for any confirmed cases. We understand the importance and urgency of this situation and really appreciate your patience. This remains a high priority for us, and we’re here to support you throughout the process. We recommend continuing to monitor your environment for unusual activity or unexpected changes. If you notice anything suspicious or believe your site may have been affected, please reach out to Support. We’ll continue to closely monitor the situation and share further updates as more information becomes available. Thank you for your patience.

Our Security and Engineering teams remain actively engaged and are continuing to investigate the affected environments. Confirmed threats are being quarantined as part of our ongoing containment efforts, while findings are reviewed and validated. We are also preparing to begin restoration work where necessary. An estimated restoration timeline is not yet available, but we will share additional details as soon as they are confirmed. This remains a high priority, and we will continue to provide updates as progress is made.

Our Security and Engineering teams continue to work on containment and remediation efforts across affected environments. Deep-system scanning remains active as we work to identify, isolate, and quarantine compromised instances. Restoration planning is also ongoing, with our technical teams validating safe recovery paths for impacted sites. While a precise time-to-resolution is still being established, restoring full system integrity safely remains our highest priority. We appreciate your continued patience as this work continues. We will provide another status update as soon as there are meaningful developments or milestones to share. If you need assistance or have any concerns, please contact our Support team.

Our Security and Engineering teams remain actively engaged in the ongoing containment, investigation, and remediation efforts across affected environments. Our teams continue to review scanning results, validate findings, and take appropriate remediation actions where potential compromise has been identified. Restoration efforts are also progressing as we work to safely return affected sites to a known-good state. We understand the importance and urgency of this situation and appreciate your continued patience. We will provide further updates as meaningful progress is made and additional remediation details become available. If you need assistance or have any concerns, please contact our Support team.

Our technical teams continue to make progress on containment, investigation, and remediation across affected environments. Adobe has recently released a patch addressing the underlying vulnerability. Our technical teams are actively reviewing, testing, and deploying the patch while continuing deep-system scans and validating safe recovery paths to restore impacted sites to a known-good state. We will continue to share updates as new remediation details become available. Please contact Support if you have any questions or require assistance in the meantime.

Our Engineering teams continue to make progress on containment, investigation, and remediation across affected environments. Adobe has recently released a patch addressing the underlying vulnerability. Our technical teams are actively applying the patch across affected environments in batches. There is no specific priority or ordering for the affected Magento versions; the rollout is progressing batch by batch, with our teams continuing to apply the patch across all affected versions. At the same time, we will continue deep-system scans and validate the patched environments to ensure safe recovery paths and restore impacted sites to a known-good state. We will continue to share updates as additional remediation details and progress become available. If you need assistance or have any concerns, please contact our Support team.

Our technical teams continue to actively work through the remediation process across affected environments. The patch rollout is progressing in batches, with teams continuing to apply the available Adobe security patch across affected Magento versions. We are also continuing system scans and validation of patched environments to help ensure affected sites can be safely restored to a known-good state. We will continue to keep clients informed as meaningful progress is made. If you need assistance or have any concerns, please contact our Support team.

Our Engineering teams have completed the patching process for all affected Magento sites where the available Adobe security patch could be successfully applied. For sites where the patch could not be applied, individual support cases have been created, and affected customers have been contacted with additional information and recommended next steps. Our patching efforts related to this incident are now complete. We encourage all customers to remain vigilant and keep their Magento installations up to date with the latest available security patches and supported versions. Thank you for your cooperation and patience while our teams worked through this security event. If you have any questions or require assistance, please reach out via chat or support case.

Our teams have identified a distributed denial of service attack (DDOS) on cloudhost-2038507.us-west-1.nxcli.net. Our network engineers are already enabled for mitigation. We will provide another update as soon as more information becomes available. If you have any questions or concerns, please contact us via live chat or case.

The mitigation has taken effect, and the server is stable and operating normally. We have closely monitored the environment and have not observed any further issues. If you experience any issues or need assistance, please reach out via Live Chat or by submitting a support case. We appreciate your patience throughout this incident.

This incident has been resolved.

We are currently investigating a performance issue affecting a subset of our servers in the au-south-1 region. Customers may experience slowness or degraded performance, and there is a potential for service interruption while the issue is being investigated. Our systems engineers have been engaged and are working to identify the cause and restore normal performance as quickly as possible. We appreciate your patience. If you have any questions or concerns, please contact us via live chat or case.

As an update regarding the ongoing latency issue: Some customers may experience increased latency and/or intermittent service interruptions when traffic traverses affected network paths in the US West region. The issue has been linked to two separate fiber cuts impacting an upstream network provider in the Los Angeles and Honolulu areas. The upstream provider's engineers are actively working to address both fiber cuts, and their third-party fiber vendor has also been engaged. Our Network Administration team is continuing to monitor the situation closely. At this time, our monitoring indicates that customer sites remain operational, though some users may experience intermittent increased latency depending on their network path. We will provide further updates as more information becomes available. We appreciate your patience and understanding.

This incident has been resolved.

We are investigating issues affecting the Nexcess Client Portal login at https://portal.nexcess.net/. Our engineering team is working to identify the cause and restore full availability as quickly as possible. We will provide updates as more information becomes available. We appreciate your patience and understanding during this time.

A fix has been implemented that resolves the issues with the portal login. We are currently monitoring the results to ensure stability.

The Nexcess Client Portal login issue has been resolved. Services are now fully operational, and no further impact has been observed.

We are aware of an issue affecting some WordPress websites using the WP Rocket plugin following the WordPress 7.1 update. This may result in website interruptions or fatal errors. Resolution: WP Rocket has released a fix in version 3.23.2.2. If your website is affected, please update the WP Rocket plugin to version 3.23.2.2 or later. If you are unable to update the plugin, WP Rocket has also provided temporary workarounds in their documentation: https://docs.wp-rocket.me/article/1927-fatal-error-on-wordpress-7-1 We will provide additional updates as more information becomes available. If you have any questions or concerns, please don't hesitate to contact us via live chat or by opening a support case.

We have completed our review of this issue and are closing this incident. The root cause was identified as a compatibility issue within the WP Rocket plugin following the WordPress 7.1 update. WP Rocket has released a fix, and customers can resolve the issue by updating the plugin to version 3.23.2.2 or later. As this involves a third-party plugin, we are not performing automated plugin updates across customer environments. However, we conducted a fleet-wide review to identify customers using affected WP Rocket versions and proactively communicated the issue, available fix, and recommended actions to those customers. Customers who continue to experience issues can contact our Support team for assistance with disabling the plugin or for guidance on updating WP Rocket to a fixed version. No further actions are pending from our side, and this incident is now considered closed.

GitHub is reporting degraded performance via their status page this morning: https://www.githubstatus.com/ Per the page, this problem may be affecting Pull Requests, Issues, Copilot, Actions, Webhooks, and API requests, among other services. Customers should follow the GitHub status page for the latest information.

This issue is currently affecting the ability to create new Magento, Wordpress, and WooCommerce websites and some dedicated cloud plans through the Nexcess customer portal. Nexcess Engineering and Development teams are currently reviewing the service impact and evaluating options to return service as quickly as possible. We will provide further updates as soon as they are available. We appreciate your patience as our team works to resolve this issue. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

This incident has been resolved.

We are currently investigating a service-impacting issue affecting the server cloudhost-4895770.us-midwest-2.nxcli.net. Our Nexcess Systems Engineering team has been engaged and is actively working to restore service as quickly as possible. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or concerns, please don't hesitate to contact us via live chat or by opening a support case.

The issue has been identified, and our teams are actively working toward a resolution. We will provide further updates as more information becomes available. Thank you for your patience.

Service has been successfully restored on the impacted cloudhost. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

This incident has been resolved.

A security vulnerability, CVE-2026-65640, has been identified in WordPress that could allow an authenticated Author-level or higher user to achieve remote code execution through a malicious file upload on sites using Imagick and Ghostscript. The vulnerability has been addressed through updates across supported WordPress branches. Patched Versions: Customers should update to the following patched version for their respective WordPress branch: 7.0.4 6.9.7 6.8.8 6.7.7 6.6.7 6.5.10 6.4.10 6.3.10 6.2.11 6.1.12 6.0.14 5.9.16 5.8.15 5.7.17 5.6.19 5.5.20 5.4.21 5.3.23 5.2.26 5.1.24 5.0.27 4.9.31 4.8.30 4.7.35 Recommended Action: Customers are strongly encouraged to update WordPress core to the latest available patched version and ensure automatic updates are enabled where appropriate. Customers with automatic updates enabled should receive the applicable update automatically. However, we recommend verifying the currently running WordPress version to ensure the security update has been successfully applied. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please reach us via live chat or via a case. Additional information: https://wordpress.org/news/2026/08/wordpress-7-0-4-release/ https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-8vr3-7mxf-gx8w

The WordPress security vulnerability CVE-2026-65640 has been addressed in the latest WordPress security releases. Customers are encouraged to keep their WordPress installations updated to the latest available security release within their current supported branch. We have proactively contacted customers identified as running potentially affected WordPress versions and provided recommendations to update their installations. At this time, the incident has been resolved, and the related status page notification will be closed.

We are currently investigating an issue affecting a subset of our servers in the us-west-1 region. Our systems engineers have been engaged and are working to restore service as quickly as possible. We appreciate your patience. If you have any questions or concerns. Please contact us via live chat or case.

Our team has now implemented a fix, and affected servers and services should be operating as expected at this time. We will continue to monitor the situation closely to ensure ongoing stability. If you have any questions or concerns, please contact us via live chat or case.

The issue affecting a subset of our servers in the us-west-1 region has been resolved. Our team has restored service, and the affected servers are operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding while we worked to resolve the issue.

A high-severity reflected XSS vulnerability, CVE-2026-64638, has been identified in the WordPress login interface. Exploitation requires a victim to visit a specially crafted URL and, under specific conditions, could potentially lead to PHP code execution. Impacted versions: WordPress 4.7 – 7.0.2 (every release on every branch) WordPress 4.6 and earlier — end of life, no patch available Fixed versions: WordPress 7.0.3 WordPress 6.9.6 WordPress 6.8.7 Equivalent minor releases on every remaining supported branch back to 4.7 Recommended Action Customers are strongly encouraged to update WordPress core and ensure automatic security updates are enabled where appropriate. Since exploitation requires user interaction, customers should also remain vigilant against phishing attempts and avoid clicking suspicious or unsolicited links. Customers with automatic security updates enabled should receive the applicable update automatically; however, we recommend verifying the currently running WordPress version. There is currently no reported evidence of widespread exploitation in the wild. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please contact our Support team.

The WordPress security vulnerability CVE-2026-64638 has been addressed in the latest WordPress security releases. Customers are encouraged to keep their WordPress installations updated to the latest available security release within their current supported branch. We have proactively contacted customers identified as running potentially affected WordPress versions and provided recommendations to update their installations. At this time, the incident has been resolved, and the related status page notification will be closed.

Our Engineers are investigating an interruption in service affecting cloudhost-2915341.us-midwest-1.nxcli.net & cloudhost-2915335.us-midwest-1.nxcli.net. We understand the inconvenience this may cause and truly appreciate your patience while we resolve the issue. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

Our Engineers have successfully restored service to the affected servers, and all services are currently operating normally. The incident is now in a monitoring state. We will continue to watch the environment closely to ensure stability following the restoration of service. We appreciate your patience throughout this incident and will provide additional updates if there are any significant changes. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

This incident has been resolved.

We are currently investigating a service-impacting issue affecting the server cloudhost-1189763.au-south-1.nxcli.net. Our Nexcess Systems Engineering team has been engaged and is actively working to restore service as quickly as possible. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or concerns, please don't hesitate to contact us via live chat or by opening a support case.

The issue has been identified, and our teams are actively working toward a resolution. We will provide further updates as more information becomes available. Thank you for your patience.

Our engineers have successfully recovered the service on the impacted cloudhost. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

This incident has been resolved.

On July 17th Wordpress.org announced two critical remote code execution (RCE) vulnerabilities commonly known as WP2Shell. These vulnerabilities exist in Wordpress Core and allow an unauthenticated request to execute arbitrary code on the target website. Customers running the Wordpress versions below are strongly advised to upgrade to latest version shown as soon as possible: Wordpress 6.8.x; fixed in 6.8.6 WordPress 6.9.x; fixed in 6.9.5 WordPress 7.0.x; fixed in 7.0.2 WordPress 7.1 beta, fixed in 7.1 beta2 Source: https://wordpress.org/news/2026/07/wordpress-7-0-2-release/

Our teams continue to work diligently to assess the impact of the recently disclosed WordPress Core vulnerabilities and verify that appropriate mitigation measures are in place. We remain actively engaged in our investigation and are monitoring the situation for any new developments. We will continue to closely monitor the situation and take any additional steps necessary to maintain system security and stability. If you need assistance or have any concerns, please contact our Support team.

The Nexcess Managed Wordpress platform configures Wordpress Core updates by default and the vast majority of websites have been updated. Nexcess System Engineers proactively attempted to update affected websites that were not already on the patched version. In some cases this was not possible to do. The Nexcess Managed Wordpress Development team has pushed a must-use plugin that mitigates this vulnerability where the application is not on a patched version. All customers are strongly encouraged to ensure their websites have been updated to the latest version of Wordpress.

This incident has been resolved.

We have encountered an issue with a CloudHost, and our engineers have identified the cause. The team is actively working towards a resolution. We understand the impact this may have and will continue to provide updates here as progress is made. In the meantime, if you have any questions, please do not hesitate to contact our Support team via chat or email.

Our Engineering team has resolved the issue, and the host is now back online. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

This incident has been resolved.