# CVE-2026-87902 — WordPress

> As of 2026-09-22, CVE-2026-87902 is a HIGH-severity vulnerability in WordPress, CVSS v3.1 8.1. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-87902, most recently “CVE-2026-87902: Critical Unauthenticated Local File Inclusion in WordPress Core (Conditional RCE)”.

**Last updated:** 2026-09-22

## 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.

The record classifies CVE-2026-87902 under weakness class [CWE-98](https://cwe.mitre.org/data/definitions/98.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 13 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.1 — HIGH (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-22

## Is CVE-2026-87902 being exploited?

Weaponised exploit code for CVE-2026-87902 is publicly available. 5 public proof-of-concept repositories are tracked for this identifier.

- [abraxas/CVE-2026-87902](https://github.com/abraxas/CVE-2026-87902) (github)
- [ressl/cve-2026-87902-poc](https://github.com/ressl/cve-2026-87902-poc) (github)
- [vulpecuna/CVE-2026-87902](https://github.com/vulpecuna/CVE-2026-87902) (github)
- [dinosn/cve-2026-87902-wordpress-lfi-lab](https://github.com/dinosn/cve-2026-87902-wordpress-lfi-lab) (github)
- [rabakuku/CVE-2026-87902-A-working-PoC-for-WordPress-s-critical-path-traversal](https://github.com/rabakuku/CVE-2026-87902-A-working-PoC-for-WordPress-s-critical-path-traversal) (github)

## Affected products and versions

- **WordPress**: WordPress

## How to fix CVE-2026-87902

No vendor patch reference has been recorded for CVE-2026-87902 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-87902

1 tracked threat in the Threadlinqs corpus references CVE-2026-87902, either in the campaign’s CVE list or as an indicator on the campaign record.

- [CVE-2026-87902: Critical Unauthenticated Local File Inclusion in WordPress Core (Conditional RCE)](https://intel.threadlinqs.com/threat/TL-2026-2623) — CRITICAL · 2026-09-22

## Sources

Enriched from CVE.org, NVD, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-09-23. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [github.com](https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-87902
Full detection coverage and IOCs for threats exploiting CVE-2026-87902 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp