CVE-2026-87902

HIGH
8.1
CVSS Score
Published: September 22, 2026 at 04:44 PM UTC
Updated: September 28, 2026 at 12:20 PM UTC
1 product affected across 1 vendorWordPress

Using WordPress by WordPress?

Get instant alerts when new vulnerabilities affect WordPress - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploitation
CISA KEV
Exploit prediction
EPSS 96%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score95.8%

EPSS (Exploit Prediction Scoring System) estimates a 95.8% chance this CVE is exploited in the wild within the next 30 days — higher than 100% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

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.

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.
Ransomware Use
Unknown
Added to KEV
Sep 25, 2026
Remediation Due
Sep 28, 2026
31 days overdue

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.7.37v < 7.1.24.8 ≤ v < 4.8.324.9 ≤ v < 4.9.335.0 ≤ v < 5.0.295.1 ≤ v < 5.1.265.2 ≤ v < 5.2.285.3 ≤ v < 5.3.255.4 ≤ v < 5.4.235.5 ≤ v < 5.5.225.6 ≤ v < 5.6.215.7 ≤ v < 5.7.195.8 ≤ v < 5.8.175.9 ≤ v < 5.9.186.0 ≤ v < 6.0.166.1 ≤ v < 6.1.146.2 ≤ v < 6.2.136.3 ≤ v < 6.3.126.4 ≤ v < 6.4.126.5 ≤ v < 6.5.126.6 ≤ v < 6.6.96.7 ≤ v < 6.7.96.8 ≤ v < 6.8.106.9 ≤ v < 6.9.97.0 ≤ v < 7.0.67.1 ≤ v < 7.1.2
Affected range stops below 4.7.37, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.32, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.9.33, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.29, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.1.26, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.2.28, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.3.25, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.4.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5.22, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.6.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.7.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.8.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.9.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.3.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.4.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.5.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.8.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.9.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.0.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.1.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-98

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card