CVE-2026-87902: WordPress Core Remote File Inclusion Vulnerability

Patch now

HIGH 8.1EXPLOITEDREMOTEUPGRADE

CVE-2026-87902 is a high-severity flaw (CVSS 8.1) affecting wordpress, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
EPSS top 1%: very likely to be exploited
Exploited in the wild (CISA KEV)
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	40.0% (top 1%)
CISA exploited list	Yes, fix due 2026-09-28
Weakness	CWE-98
Published	2026-09-22
Last modified	2026-09-28

Publisher (CNA): HackerOne · Vendor: wordpress

Last updated 2026-09-28 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-22 17:17 UTCPublished CVE record published
2026-09-25Exploited Added to the CISA Known Exploited Vulnerabilities list
2026-09-28Deadline CISA due date for US federal agencies to patch
2026-09-28 12:20 UTCUpdated Record last modified

wordpress wordpress UPGRADE

Affected: < 4.7.37 · >= 4.8 and < 4.8.32 · >= 4.9 and < 4.9.33 · >= 5.0 and < 5.0.29 · >= 5.1 and < 5.1.26 · >= 5.2 and < 5.2.28 · >= 5.3 and < 5.3.25 · >= 5.4 and < 5.4.23

Fixed in: 4.7.37, 4.8.32, 4.9.33, 5.0.29, 5.1.26, 5.2.28, 5.3.25, 5.4.23, 5.5.22, 5.6.21, 5.7.19, 5.8.17, 5.9.18, 6.0.16, 6.1.14, 6.2.13, 6.3.12, 6.4.12, 6.5.12, 6.6.9, 6.7.9, 6.8.10, 6.9.9, 7.0.6, 7.1.2

Safe to downgrade to: a release before 4.8

1. Check installed version

apt-cache policy wordpress || rpm -q wordpress || wordpress --version

2. UPGRADE to 4.7.37 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wordpress

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wordpress

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.8 (Debian / Ubuntu)

apt-cache madison wordpress sudo apt install wordpress=<VERSION_BEFORE_4.8> sudo apt-mark hold wordpress

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wordpress sudo dnf downgrade wordpress-<VERSION_BEFORE_4.8> sudo dnf versionlock add wordpress

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora 46 · uv · FIXED · 0.13.5-2.fc46 · FEDORA-2026-0a45cde16b · source

sudo dnf upgrade --advisory=FEDORA-2026-0a45cde16b

Fedora ELN · oo7 · FIXED · 0.7.0~beta-3.eln159 · FEDORA-2026-f348262964 · source

sudo dnf upgrade --advisory=FEDORA-2026-f348262964

Debian 12 · wordpress · NO FIX YET

Debian 13 · wordpress · FIXED · 6.8.10+dfsg1-0+deb13u1

sudo apt update && sudo apt install --only-upgrade wordpress dpkg --compare-versions "$(dpkg-query -W -f='${Version}' wordpress)" ge "6.8.10+dfsg1-0+deb13u1" && echo PATCHED || echo STILL-VULNERABLE

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: ressl/cve-2026-87902-poc (43 stars)
GitHub PoC: abraxas/CVE-2026-87902 (35 stars)
GitHub PoC: tc4dy/CVE-2026-87902-Toolkit (14 stars)
Write-up: patchstack.com/articles/cve-2026-87902-attackers-started-probing-wordpress-sites-hours-aft
Exploit-DB: WordPress 7.0.2 - Path Travesal
Nuclei scan template: WordPress Core - PHP Template Path Traversal

Advisories and coverage

Research and news

Patchstack: WordPress 7.1.3 Security Release 2026-10-06
Patchstack: CVE-2026-87902: Attackers Started Probing WordPress Sites Hours After the Patch 2026-09-22

Verify at the official source NVD · CVE Program · CISA KEV catalog · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-87902?

wordpress: upgrade to 4.7.37, 4.8.32, 4.9.33, 5.0.29, 5.1.26, 5.2.28, 5.3.25, 5.4.23, 5.5.22, 5.6.21, 5.7.19, 5.8.17, 5.9.18, 6.0.16, 6.1.14, 6.2.13, 6.3.12, 6.4.12, 6.5.12, 6.6.9, 6.7.9, 6.8.10, 6.9.9, 7.0.6, 7.1.2. Exact commands for each OS are on this page.

Is CVE-2026-87902 being exploited?

Yes. CVE-2026-87902 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

What does CVE-2026-87902 affect?

CVE-2026-87902 affects wordpress. Severity is high (CVSS 8.1). 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 me

How urgent is CVE-2026-87902?

Priority 88/100. High severity; EPSS top 1%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs