Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-87902 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

37 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-87902 using CVSS 8.1, EPSS 3%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highpublic exploit

CVE-2026-87902

CVE-2026-87902 — An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the…

Q: What is CVE-2026-87902?

CVE-2026-87902 is An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the…. The supplied enrichment data classifies it as Unclassified mapped to CWE-98 CWE-98.

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.

Published Sep 22, 2026Updated Sep 22, 2026Sources: NVD, WordPress (CNA), GitHub, Red Hat (VEX)

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

chance of exploitation in 30 days

Affects

WordPress

CVSS base

8.1

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade WordPress to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2026-87902

fixed0affected0not affected1

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
WordPress	WordPress	0 to < 7.1.2	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.1	CVSS 3.1	high	2.2	5.9	CNA, Red Hat (VEX)

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

CWE-98

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable WordPress.
Monitor for scanner or exploit-pattern traffic after 37 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.1 (AV:N)
Sep 22, 2026 · NVD
Initial · CVE published
Sep 22, 2026 · NVD

References

3 on the record

github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp
Exploit, Third Party Advisory
access.redhat.com/security/cve/CVE-2026-87902
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2026-87902
Vendor Advisory

Coverage

4 stories from the feeds we poll

Elsewhere on this site

WordPressevery CVE for this vendor
Unclassifiedsame class
CWE-98other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-87902 is An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the…, a high vulnerability affecting WordPress from WordPress. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 37 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.1 describes technical severity, while EPSS 3% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.