What the official KEV catalog reports
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.
Action in the CISA catalog
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.
Additional CISA notes: https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp ; ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-87902
The CISA due date refers to covered federal-agency obligations where applicable; it is not automatically a private-sector deadline. Catalog inclusion documents known exploitation, not whether your own system is vulnerable. Check official sources before acting.
How to decide whether your systems are affected
- Check your software inventory. Look for WordPress Core across managed computers, servers, appliances, and cloud services where applicable. Record the asset IDs and deployed versions. A matching product name alone is not proof of exposure.
- Validate affected versions and mitigations. Read the current vendor advisory and NVD entry for CVE-2026-87902. Compare the affected configuration, version, and prerequisites to each asset before marking it exposed.
- Plan and verify an authorized response. Follow current vendor guidance, test changes, document the owner and remediation date, and confirm the issue is resolved with a targeted check or rescan. Escalate uncertainty rather than guessing.
Evidence to keep for a defensible decision
For assets that need remediation, retain a record of the CVE, affected asset, discovery source, advisory reference, approval, action taken, and validation result. For assets found not to be affected, retain the version or configuration evidence supporting that decision.
Use the free KEV triage worksheet → · Learn about scan-to-POA&M evidence →