Skip to content
Server Security Center
KEVhigh8.1

CVE-2026-87902: WordPress Core Remote File Inclusion

WordPress Core · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-25.

CVSS v3.1 (CVE record)
8.1
high
EPSS (exploit probability, 30 days)
96%
higher than 99.8% of all CVEs
Added to CISA KEV
2026-09-25
US federal due date 2026-09-28
Ubuntu priority
high

CVE-2026-87902 explained

CVE-2026-87902 is a file inclusion flaw in WordPress Core page-template resolution. An unauthenticated attacker can make the get_page_template() function include a chosen readable local PHP file outside the active theme directories. Under certain server and theme conditions this can lead to remote code execution. CISA lists it as known exploited.

Impact

A remote attacker needs no account and no user interaction. Exploitation has high complexity because specific pre-conditions on both the server and the active theme must be met. When they are, the attacker can run code on the server. This gives full compromise of confidentiality, integrity and availability for the WordPress site and the data it can reach.

Who is affected

The wordpress source package is affected. Fixed versions exist for Debian 13 (trixie) in 6.8.10+dfsg1-0+deb13u1 and for Debian 14 (forky), the testing distribution, in 7.1.2+dfsg1-1. No fixed version is published for Debian 12 (bookworm), Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS or Ubuntu 26.10. Ubuntu 18.04 LTS and Ubuntu 20.04 LTS have no fix published; their fixes come only through Ubuntu Pro (ESM). Ubuntu 16.04 LTS is end of life and has no fix.

Written with AI from the data on this page and checked against it automatically.

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

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • WordPress
    Affected
    • < 7.1.2
    Fixed in
    • 7.1.2

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. On Debian 13 (trixie), update wordpress to 6.8.10+dfsg1-0+deb13u1 or later.
  2. On Debian 14 (forky), update wordpress to 7.1.2+dfsg1-1 or later.
  3. Restart the web server and PHP processes so the updated code is loaded.
  4. On releases without a fix, apply the mitigations below and watch the distribution advisory for an update.
  5. Upgrade systems running Ubuntu 16.04 LTS to a supported release.
  6. Because the flaw is known exploited, review affected sites for signs of compromise.

Until a fixed wordpress package is published for your release, limit network exposure of affected sites, for example by restricting access to trusted networks. Follow the vendor's mitigation instructions. Consider taking unpatched public sites offline if mitigations are unavailable. Ubuntu 18.04 LTS and 20.04 LTS users should watch for fixes via Ubuntu Pro (ESM). Ubuntu 16.04 LTS is end of life and should be upgraded rather than waiting.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace wordpress with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="wordpress"'

2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="wordpress"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

No fixed version yet on 7 releases

Ubuntu 26.10, Ubuntu 26.04 LTS, Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Ubuntu 20.04 LTS, Ubuntu 18.04 LTS, Debian 12 (bookworm): no fixed version of wordpress yet, so every installed version there is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: github.com/WordPress/wordpress-develop/security/advisorie…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-98 Remote File Inclusion

Questions about CVE-2026-87902

Does an attacker need to log in to WordPress?
No. The flaw can be triggered by an unauthenticated remote attacker without user interaction. Code execution, however, depends on pre-conditions on both the server and the active theme being met.
Is this vulnerability being exploited?
Yes. CISA added CVE-2026-87902 to its Known Exploited Vulnerabilities catalog on 2026-09-25, with a US federal due date of 2026-09-28. Whether it has been used in ransomware campaigns is unknown.
Is my Debian 12 or Ubuntu system protected after a normal update?
Not yet. No fixed wordpress version is published for Debian 12 (bookworm) or the listed Ubuntu releases. Only Debian 13 (trixie) and Debian 14 (forky) have fixed packages. Apply mitigations until a fix arrives.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.