// Güvenlik

Update released for critical unauthenticated vulnerability in WordPress core

Version 7.1.2 has been released for CVE-2026-87902, which opens the door to executing code without logging in in the WordPress core; the fix was also backported to older branches as far back as 4.7.

A path traversal vulnerability in the WordPress core that could open the door for attackers to execute code without logging in to the site has been closed. The vulnerability was recorded as CVE-2026-87902 and fixed in version 7.1.2. The WordPress team backported the fix as far back as the 4.7 branch for those using older versions.

The security advisory on GitHub classifies the vulnerability as critical and gives it an impact score of 9.2. The CVSS 3.1 score on NVD’s side is 8.1. Robert Ressl discovered the vulnerability and reported it through the responsible disclosure process.

Where is the problem

The bug arises in the resolution of page templates. The get_page_template() function can include a .php file that lies outside the active theme’s directories and is readable on the server into the template. The person sending the request does not need to have an account; that is, an attacker who is not a member of the site can also try this path.

Under what conditions does it turn into code execution

According to the advisory, there are two preconditions for the vulnerability to lead to code execution. First, there must be a top-level folder whose name starts with page- inside the active theme or its parent theme. Among old default themes, Twenty Twelve and Twenty Fourteen are in this situation; popular third-party themes such as Neve, Hestia, and Sydney are also counted among those affected. Second, there must be a .php file on the server that the web user can read. Researchers note that when the register_argc_argv setting is enabled in PHP, the known pearcmd.php method can be used at this step. The official Docker php image and the default cPanel configuration before PHP 8.5 are among the affected environments.

What should you do

Update the core from the admin panel or the command line. The maintenance release corresponding to your version branch is as follows: 7.1.2, 7.0.6, 6.9.9, 6.8.10, 6.7.9, 6.6.9, and 6.5.12. Patches were also released up to 4.7.37 for those remaining on older branches. Sites with minor version automatic updates enabled will receive the new version automatically; if you have disabled automatic updates, start the process manually.

The details of the vulnerability are now public. There is no report that it has been exploited, but on a site that meets the conditions, a single request from an attacker is enough to leave it vulnerable. So do not delay updating.

Source: NVD · WordPress Security Advisory

// JOIN THE CONVERSATION

Share your experience

Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.

// KEEP READING

One more note.

All posts ↗︎