Flat vector banner showing a WordPress site shield with a cracked file path symbol

WordPress released a fix for a critical flaw in its core software on September 22, 2026. The bug, tracked as CVE-2026-87902, carries a severity score of 9.2 out of 10 and allows attackers to run their own code on a site. Attack traffic targeting the flaw grew tenfold by the following day.

What is going on

The flaw sits in the part of WordPress that decides which page template to load. It is a path traversal bug, meaning an attacker can trick the software into opening a file somewhere else on the server instead of the intended one.

Think of a receptionist who is asked to fetch file number 12, but accepts directions to walk down the hall and open any cabinet instead. Because WordPress then runs the file it was handed, the attacker can get their own code executed.

No login is needed. In observed attacks, intruders wrote files such as poc87902.php into the server's /tmp folder, then loaded them through the flaw.

Diagram of the CVE-2026-87902 attack: request, template resolver, server file, code execution, patch
How the path traversal bug turns a page request into code execution.

Who is affected

The flaw is in WordPress core, not in a single plugin or theme. Versions 4.7 through 7.1.1 are affected, which covers a very large share of WordPress sites.

It is fixed in WordPress 7.1.2. If you run an older branch, your release line may have its own backported security update.

What to do now

  1. Update WordPress to 7.1.2, or to the patched release for your branch, as soon as you can.
  2. Confirm the update actually applied. Open your WordPress dashboard and check the version number shown under Updates.
  3. If you rely on automatic updates, verify they ran. Automatic updates can silently fail on sites with file permission restrictions.
  4. Look in the /tmp and /var/tmp folders on your server for unexpected PHP files, such as anything resembling poc87902.php.
  5. Review your web server access logs for unusual requests around and after September 22, 2026.

If you find an unfamiliar PHP file or suspect the site was reached, ask your host or developer to help before simply deleting it.

How to check your own site

Our free Website Security Check reports your public CMS version, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps, so you can confirm your WordPress version is current. For deeper coverage you can run a full scan, which adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress deep scans and exposed-file and secret checks, on sites whose ownership you have verified.

Source: BleepingComputer, September 2026.