CVE-2026-87902: WordPress Core Remote File Inclusion Vulnerability

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run WordPress Core. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-09-25, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-09-28; treat that as the outer limit, not the target.
• EPSS 40.0%, percentile 99: FIRST’s model estimates a 40.0% chance of exploitation activity in the next 30 days, higher than 99% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Editorial verdict: Act now. WordPress Core: Page-Template File Inclusion to RCE — Every WordPress branch back to 4.7 was affected, no login is needed, public scanning tooling exists and attackers are already writing files through pearcmd.php, so confirm you are on a fixed release today.

What it is

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

CISA’s summary

WordPress Core contains a remote file inclusion vulnerability which could allow an unauthenticated attacker to make page-template resolution include a chosen readable local `.php` file outside the active theme directories, leading to remote code execution.

Weakness type: CWE-98.

Product: WordPress Core · Assigned by: hackerone · Published: 2026-09-22

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: high (needs special conditions)
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2026-09-25; federal due date 2026-09-28. Known ransomware use: Unknown.
• CISA required action: 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 SSVC assessment: exploitation active, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 39.98% probability of exploitation activity in the next 30 days; percentile 99.

Timeline

• 2026-09-22 — CVE record published by hackerone
• 2026-09-22 — erroneo.us brief: WordPress Core: Page-Template File Inclusion to RCE
• 2026-09-25 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2026-09-26 — CVE record last updated
• 2026-09-28 — CISA remediation deadline for US federal agencies

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (github.com) github.com

Vulnerability records

1. CVE.org record CVE-2026-87902 cve.org
2. NVD entry CVE-2026-87902 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov
2. Listed in CISA KEV notes (cisa.gov) cisa.gov
3. Listed in CISA KEV notes (cisa.gov) cisa.gov

Other references from the CVE record and advisory

1. patchstack.com patchstack.com

All exploited WordPress vulnerabilities · Today’s Security Digest