DE EN IT

~/exploited / cve-2026-87902

CVE-2026-87902: WordPress Core

According to CISA this vulnerability is already used in attacks (added on 25 September 2026).

Key facts

CVECVE-2026-87902
VendorWordPress — Core
VulnerabilityWordPress Core Remote File Inclusion Vulnerability
Added25 September 2026
Deadline (US agencies)28 September 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score8.1 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack over the network, complexity: high, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 95.77%. Higher than 99.9% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-98
Affected versionswordpress: < 4.7.37
wordpress: >= 4.8, < 4.8.32
wordpress: >= 4.9, < 4.9.33
wordpress: >= 5.0, < 5.0.29
wordpress: >= 5.1, < 5.1.26
wordpress: >= 5.2, < 5.2.28
wordpress: >= 5.3, < 5.3.25
wordpress: >= 5.4, < 5.4.23
and 17 more

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

WordPress Core contains a remote file inclusion vulnerability which could allow an unauthenticated attacker to make page-template resolution include a chosen readable local `.php` file outside the active theme directories, leading to remote code execution.

Required action (CISA)

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.

What admins should do now

  1. Affected? Check whether WordPress Core is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 25 September 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).