What is WordPress CVE-2026-87902?
WordPress's security advisory describes an unauthenticated path traversal in page-template resolution: an attacker can make get_page_template() include a chosen readable local .php file outside the active theme directories. When the server and theme meet certain conditions, that leads to remote code execution. The fix was backported to every branch back to 4.7.
The advisory rates it CVSS 4.0 9.2, while NVD shows CVSS 3.1 8.1. CISA added CVE-2026-87902 to its Known Exploited Vulnerabilities catalog on September 25, 2026, with a September 28 due date. CISA describes it as remote file inclusion; the advisory describes local file inclusion through path traversal.
Which WordPress versions are affected?
- WordPress core from 4.7 through 7.1.1 on every branch before its fixed release.
- Fixed releases include 7.1.2, 7.0.6, 6.9.9, 6.8.10, 6.7.9 and 6.6.9, with fixes on every older branch back to 4.7.37.
- Code execution needs preconditions: an active theme with a top-level directory starting with
page-, and a readable PHP file to include, such aspearcmd.phpwithregister_argc_argvon.
How to check if you're affected
- Check each site's WordPress version in wp-admin or with
wp core version. - Check whether the active parent or child theme has a top-level directory whose name starts with
page-. The advisory names Twenty Twelve, Twenty Fourteen, Neve, Hestia and Sydney. - Check whether the PHP image or host ships
pearcmd.phpwithregister_argc_argvon. The advisory says the official Docker PHP image is affected.
What to do now
- Update WordPress core to the fixed release for your branch.
- If you can't update immediately, remove or disable themes with
page-directories and turn offregister_argc_argvin PHP. - Review sites for files and admin users you didn't create since late September.
Why preconditions don't make a bug safe
This flaw needs a particular theme layout and a particular PHP file to become code execution, and both are common defaults. Exploit chains are built from exactly these ordinary pieces. When an advisory lists preconditions, check your fleet for them, but patch everywhere rather than betting each site misses one.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify moves actively exploited vulnerabilities in the dependencies and images you use up the backlog as soon as they're disclosed, and prepares the version change as a pull request for each owner to review.
The vulnerable version is set in your dependency manifests, lockfiles or images, which is where to look.
Frequently Asked Questions
Which WordPress versions fix CVE-2026-87902?
The fix is in 7.1.2, 7.0.6, 6.9.9, 6.8.10 and the matching release on every older branch back to 4.7.37. Update to the fixed release for the branch you run.
Is every WordPress site exploitable through CVE-2026-87902?
Code execution needs an active theme with a top-level directory starting with page- and a readable PHP file to include, such as pearcmd.php with register_argc_argv on. Both are common, so patch regardless.
Is CVE-2026-87902 exploited in the wild?
Yes. CISA added CVE-2026-87902 to its Known Exploited Vulnerabilities catalog on September 25, 2026, which means it has evidence of active exploitation. It gave US federal civilian agencies until September 28 to fix it. Treat exposed WordPress instances as urgent.
Update Log
- Nov 17, 2026: page published from the primary sources linked above.