How severe is CVE-2026-87902?

No CVSS score has been assigned to CVE-2026-87902 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-87902?

CVE-2026-87902 affects the following packages: wordpress (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-87902?

Update wordpress to 7.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-87902 is resolved across your whole dependency graph.

How do I detect CVE-2026-87902 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wordpress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-87902 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-87902 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2026-87902, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-87902?

CVE-2026-87902 has an EPSS (Exploit Prediction Scoring System) score of 46.1%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2026-87902 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-87902 (WordPress Core Remote File Inclusion Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-09-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-09-28. The required action was: 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. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-87902?

CVE-2026-87902 is classified as CWE-98 (CWE-98). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2026-87902?

A Nuclei detection template exists for CVE-2026-87902, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-87902 published, and has it been updated?

CVE-2026-87902 was published on September 29, 2026 and was last updated on October 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-87902 — wordpress

CVE-2026-87902 is a CWE-98 vulnerability in wordpress. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-09-25) — treat it as actively exploited and patch now. A fix is available for wordpress — see the affected versions and patch details below.

Also known asBIT-wordpress-multisite-2026-87902

Published

Sep 29, 2026

Updated

Oct 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

9 known

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-09-25. Federal agencies were required to remediate by 2026-09-28.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-87902.

EPSS Exploitation Probability

via FIRST.org ↗

46.1%probability of exploitation in next 30 days

High Risk+26.36%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦wordpress

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`wordpress`	all versions	7.1.2

Affected Products

1 product · 25 configurations

Application

wordpresswordpress

≥ 7.1 && < 7.1.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52690webappsmultiple

WordPress 7.0.2 - Path Travesal

by Robert Ressl · Oct 1, 2026

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wordpress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wordpress to 7.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-87902 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2026-87902

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-87902 -u https://target

Template: WordPress Core - PHP Template Path Traversal
Severity: critical
Impact: An unauthenticated attacker can include local PHP files outside the active theme. Depending on the files present and the PHP configuration, this can disclose sensitive data or lead to arbitrary code execution.
Remediation: Update WordPress to a patched maintenance release for the installed branch.

Template by ProjectDiscovery nuclei-templates (Hadrian, FLX), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-87902 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works