NGINX HTTP/2 flaws put WordPress servers at risk
NGINX HTTP/2 vulnerabilities are putting affected WordPress servers at risk of remote code execution, meaning an attacker may be able to run commands on a server from a distance. NGINX has released fixes for CVE-2026-123007 and CVE-2026-123633, two critical flaws in the software that can handle web traffic before it reaches PHP or WordPress.
NGINX lists versions 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 as affected by CVE-2026-123007. CVE-2026-123633 affects versions starting with 1.19.7. The corrected open-source releases are 1.30.7, the stable branch, and 1.31.9, the mainline branch. NGINX released both versions on November 18, 2026.
Both vulnerabilities require the server to accept HTTP/2, a newer way for browsers and servers to exchange web requests. HTTP/2 is disabled unless the server configuration enables it. NGINX source builds do not include the HTTP/2 module by default, while NGINX’s prebuilt packages do include it. Hosting setups differ, so the installed version alone may not show whether a site is exposed.
CVE-2026-123633 has an additional condition. NGINX must be forwarding requests to another application server while one of its workers is running low on available connections. NGINX may serve a WordPress site directly or operate in front of the application server, which means it can process HTTP/2 traffic before requests reach PHP and WordPress. Successful exploitation could allow code to run with the permissions of the NGINX worker, placing websites and other data on the same server at risk.
Updating WordPress, plugins, themes or Wordfence does not repair NGINX. The Wordfence firewall works at the PHP application layer, and a Wordfence scan cannot confirm whether the server package has been patched. The required fix must be installed by the hosting provider, server administrator or another party responsible for the operating system and web server.
F5 rates CVE-2026-123007 as Critical, with a score of 9.2 under CVSS version 4.0. F5’s second advisory gives CVE-2026-123633 the same rating. Wiz reports code execution in laboratory testing for both flaws, while Metnir reports it for CVE-2026-123633. Rapid7 published a proof of concept for remote code execution against CVE-2026-123007 using a freshly started local Docker target. That demonstrated method needs substantial traffic, but Rapid7’s result does not rule out other attack methods.
Xint, which F5 credits with discovering CVE-2026-123007, reports code execution over public HTTPS on AWS, GCP and Azure while normal traffic was running concurrently. Xint also reports chaining the NGINX flaw with a separate Linux kernel vulnerability to obtain root access in its tests. Root access is the highest level of control on a Linux system. CERT-EU reported that it knew of no exploitation in the wild on November 18.
The right response depends on who manages the server. Owners of managed or shared WordPress hosting should monitor their provider’s security announcements and status updates for guidance on CVE-2026-123007 and CVE-2026-123633. If a provider has not yet published an update, continue checking its official channels rather than assuming that an application security scan can verify the NGINX patch.
Administrators of self-managed systems should check the installed NGINX package and the active HTTP/2 configuration, including reverse proxies and containers. A reverse proxy is a service that receives web requests and passes them to another server. A public HTTP/2 connection may end at a content delivery network, or CDN, instead of at the NGINX origin server, so administrators must also examine the origin and any direct route to it. Vendor packages may contain backported fixes while retaining older NGINX version numbers, so administrators should follow the relevant vendor advisory instead of relying only on the displayed version.
Self-managed installations should be upgraded to 1.30.7, 1.31.9 or the vendor’s fixed package, followed by an NGINX restart so the new program is loaded. Containers should be recreated from patched images. Administrators using NGINX Plus should check F5’s fixed releases for both CVEs.
If an affected NGINX listener cannot be updated immediately, administrators can temporarily disable HTTP/2. They should remove http2 from the relevant listen directives. On NGINX 1.25.1 or later, they should also set http2 off;. The configuration must then be tested and reloaded, followed by a check that the listener no longer accepts HTTP/2. This is only a temporary measure for these two attack paths and does not fix other vulnerabilities addressed in the same NGINX release.
Metnir says it found CVE-2026-123633 on August 29, 2026, and reported it to F5 on September 12. Xint says it discovered CVE-2026-123007 on October 11 and reported it to F5 through HackerOne on October 16. NGINX released the fixed versions on November 18. AEU Hosting provides managed WordPress hosting, secured end to end, which is relevant for site owners who do not want to maintain every server component themselves. The immediate priority for every NGINX user remains confirmation that the responsible host or administrator has applied the correct fix.