◆ CVE Hub

CVE-2026-87902

KEV: known exploited SSVC: active
Published
2026-09-22
Last modified
2026-09-28
CNA
hackerone
NVD status
Analyzed
CWE
CWE-98
CVSS v3.1 (listed by NVD)
8.1
HIGH
Scored by CISA-ADP (not yet scored by NVD)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0 (listed by NVD)
—
Not scored
CVSS (listed by CVE.org)
—
Not scored
EPSS exploit probability
40.0%
Percentile 98.6%
as of 2026-10-24
CISA KEV
Listed
Added 2026-09-25 / due 2026-09-28
Ransomware use: Unknown
SSVC (CISA ADP)
active
Automatable: no / Impact: total

Attack conditions and impact

Derived from the CISA-ADP (via NVD) CVSS 3.1 vector
NetworkNo authNo interactionConditions Confidentiality HIntegrity HAvailability H

This vulnerability may be exploitable over the internet without authentication or user interaction.

MetricValueMeaning
Attack vector AVNNetwork
Attack complexity ACHHigh (conditions required)
Privileges required PRNNone
User interaction UINNone
Scope SUUnchanged
Confidentiality CHHigh
Integrity IHHigh
Availability AHHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Description

NVD

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.

Workarounds (CNA)

WordPress 7.1.2 has been released containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7.

CISA KEV entry

WordPress Core Remote File Inclusion Vulnerability — WordPress / Core

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.

https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp ; ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-87902

CVSS assessments

ProviderVersionScoreVector
NVD / 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary)3.18.1 HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
ADP / CISA-ADP3.18.1 HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products and packages

CNA (CVE.org)

VendorProductVersions
WordPressWordPress
affected: 0 … < 7.1.2
default: unaffected

NVD CPE (25)

Show CPE list
VendorProductRangeCPE
wordpresswordpress< 4.7.37cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 4.8, < 4.8.32cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 4.9, < 4.9.33cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.0, < 5.0.29cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.1, < 5.1.26cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.2, < 5.2.28cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.3, < 5.3.25cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.4, < 5.4.23cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.5, < 5.5.22cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.6, < 5.6.21cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.7, < 5.7.19cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.8, < 5.8.17cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 5.9, < 5.9.18cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.0, < 6.0.16cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.1, < 6.1.14cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.2, < 6.2.13cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.3, < 6.3.12cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.4, < 6.4.12cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.5, < 6.5.12cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.6, < 6.6.9cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.7, < 6.7.9cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.8, < 6.8.10cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 6.9, < 6.9.9cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 7.0, < 7.0.6cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*
wordpresswordpress>= 7.1, < 7.1.2cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*

Linux distribution status

Red Hat ↗

No record

Debian ↗

ReleasePackageStatusFixed version / notes
bookwormwordpressopen not yet assigned
forkywordpressresolved not yet assigned7.1.2+dfsg1-1
sidwordpressresolved not yet assigned7.1.2+dfsg1-1
trixiewordpressresolved not yet assigned6.8.10+dfsg1-0+deb13u1

Ubuntu ↗

No record

References (3)