← Back to CVE intelligence
CVE intelligenceCISA KEV

CVE-2026-87902

WordPress Core Remote File Inclusion Vulnerability

Published Sep 22, 2026Sources checked Nov 20, 2026
8.1HIGHCVSS out of 10
What this means

Actively exploited

CISA lists CVE-2026-87902 in its Known Exploited Vulnerabilities catalog, which means exploitation has been observed. The entry applies to WordPress Core.

  • Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Public exploit: Public PoC available.

  • Patchstack: Exploitation progresses beyond initial probing (2026-09-23)

    Patchstack's September 23 update reports attempts to write attacker-controlled PHP files, including command-executing payloads. Its September 22 report described reconnaissance. This is provider-reported attack activity, not evidence that a particular customer's site was compromised.

  • Robert Ressl: Researcher publishes proof-of-concept code (2026-09-22)

    The discoverer's public repository documents a lab demonstration of local PHP inclusion and conditional code execution. Required theme and PHP configuration are documented. SecurityAlert verified the publication, not execution of the exploit.

  • WordPress: WordPress publishes fixed releases and prerequisites (2026-09-22)

    The vendor lists affected and patched versions by branch, including 7.1.2, 7.0.6, 6.9.9 and backports through 4.7.37. Code execution depends on the active theme layout and readable PHP files, with additional prerequisites for the demonstrated PEAR chain.

  • BleepingComputer: Reporting covers malicious payload delivery (2026-09-23)

    BleepingComputer reports the escalation from probing to payload delivery, citing Patchstack. This is coverage of the same underlying observations, not an independent second detection.

  • Exploit-DB: WordPress 7.0.2 - Path Travesal (2026-10-02 04:34:03.012279+00)

    Exploit-DB lists a public exploit or proof of concept for this CVE. SecurityAlert has not executed it; this is not evidence of attacks against your systems.

What to do next

Remediation and response

  • Update to WordPress 7.1.2 or the fixed release for your branch listed in the WordPress advisory.
  • Review access logs for traversal in pagename and requests referencing pearcmd. Investigate unexpected PHP files and signs of execution; patching alone does not rule out an earlier compromise.
  • Check the theme and PHP prerequisites in the advisory. The published code-execution chain is conditional, not proof that every WordPress installation is exploitable.
CISA KEVListedObserved exploitation
EPSS95.8%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors2Source-linked actor relationships
Overview

What is CVE-2026-87902?

An unauthenticated attacker can make `get_page_template()` 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 RCE.

Source: NVD

Vendor context

The vendor lists affected and patched versions by branch, including 7.1.2, 7.0.6, 6.9.9 and backports through 4.7.37. Code execution depends on the active theme layout and readable PHP files, with additional prerequisites for the demonstrated PEAR chain.

WordPress · Published Sep 22, 2026
Reported activity

Patchstack's September 23 update reports attempts to write attacker-controlled PHP files, including command-executing payloads. Its September 22 report described reconnaissance.

This is provider-reported attack activity, not evidence that a particular customer's site was compromised.

Patchstack · Published Sep 23, 2026
CISA says:Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.CISA catalog due date Sep 28, 2026