A critical WordPress vulnerability (CVE-2026-87902) scores 9.2/10 and affects releases going back to 4.7 through 7.1.1; fixes are released in 7.1.2 and backported to all supported branches. The flaw is an unauthenticated path traversal in page-template resolution (get_page_template()) that allows inclusion of an attacker-chosen readable local .php file outside active theme directories, creating a conditional remote code execution (RCE) vector. The weakness is classified as CWE-98 (improper control of filename for include/require) and is exploitable over the network with low complexity, no privileges, and no user interaction, yielding high impact to confidentiality, integrity, and availability.
Exploitation requires two specific preconditions: the active theme (child or parent) contains a top-level directory whose name begins with "page-" (affecting legacy Twenty Twelve and Twenty Fourteen and some popular third-party themes such as Neve, Hestia, and Sydney), and a readable local .php target exists on the server. Known escalation paths include the pearcmd.php PEAR→RCE transition when register_argc_argv is On; the official PHP Docker image and default cPanel setups with PHP prior to 8.5 are noted as vulnerable. The issue was discovered and responsibly disclosed by Robert Ressl.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.