Sources report that an unauthenticated attacker can make WordPress Core include a local PHP file during page-template resolution, which can lead to remote code execution under certain conditions. CISA lists it as exploited.
What is affected
The vulnerability is tracked as CVE-2026-87902 and affects WordPress Core, the WordPress content management system itself. It was disclosed on 2026-09-22. The sources list these affected version ranges:
< 4.7.37≥ 4.8, < 4.8.32≥ 4.9, < 4.9.33≥ 5.0, < 5.0.29≥ 5.1, < 5.1.26≥ 5.2, < 5.2.28≥ 5.3, < 5.3.25≥ 5.4, < 5.4.23
A range such as < 4.7.37 means the versions before 4.7.37. The weakness is classified as CWE-98. Any site that runs WordPress Core in one of these ranges is in scope, including sites operated for you by a hosting provider or an agency.
What the flaw allows
The sources describe that an unauthenticated attacker can make page-template resolution include a chosen, readable local PHP file outside the active theme directories. If relevant pre-conditions for both the server and the active theme are met, this can lead to remote code execution. The description does not spell out those pre-conditions, so the WordPress security advisory is the place to read them.
The NVD records a CVSS 3.1 base score of 8.1, which is high severity. The vector records network access, no privileges required, no user interaction and high attack complexity, with high impact on confidentiality, integrity and availability. Details are on the NVD entry for this vulnerability.
Exploitation
CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-09-25. CISA's stated due date for US federal agencies is 2026-09-28. CISA lists known ransomware use as unknown. The catalogue is available on the CISA Known Exploited Vulnerabilities page.
Because the vulnerability is listed as exploited, treat it as a priority and do not wait for a routine maintenance window.
What to do
Identify every site you run on WordPress Core and compare its version with the ranges above. The vendor advisory lists the fixed releases and explains how to assess exposure. CISA's required action is to apply mitigations in accordance with vendor instructions. Patchstack has also published an article on this vulnerability. See the mitigation section for the steps.
What to do
Compare the version of each WordPress Core installation you run with the affected ranges, then follow the WordPress security advisory, which lists the fixed releases and the vendor's instructions. CISA's required action is to apply mitigations in accordance with vendor instructions. If your site is managed by a provider or an agency, ask them to confirm the status in writing.
Sources
- https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp
- https://nvd.nist.gov/vuln/detail/CVE-2026-87902
- https://patchstack.com/articles/cve-2026-87902-attackers-started-probing-wordpress-sites-hours-after-the-patch/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog