CVSS base score: 8.1 (High) CISA · v3.1
Score assigned by CISA's Vulnrichment program; the vendor's CVE record did not include one. Vulnrichment source record →
WordPress Core Remote File Inclusion Vulnerability
Vendor: WordPress Product: Core
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.
| Date | Source | Article |
|---|---|---|
| 2026-09-28 | Check Point Research | 28th September – Threat Intelligence Report |
| 2026-09-24 | The Hacker News | Attackers Exploit WordPress CVE-2026-87902 Within Hours of Disclosure |
| 2026-09-23 | BleepingComputer | Hackers start exploiting critical WordPress flaw for code execution |
Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.
| Date | Advisory | Issuer |
|---|---|---|
| 2026-09-25 | CISA Adds One Known Exploited Vulnerability to Catalog | CISA |
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 43 points from 2026-09-24, tracked daily from 2026-09-24; earlier points are weekly, which dates a spike to within a week. Peak probability 95.8% on 2026-10-25.
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (CC0) and filtered to repositories that are
still online, contain code, and are starred or at least two weeks old. They are
still not vetted: some are fakes and some are malware. Treat
them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm
an exploit was referenced but carry no date. This product uses data from the
NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0;
its individual Vulnerability Tests are licensed
GNU GPL v2.
| First seen | Tool | Evidence | Earliest reference |
|---|---|---|---|
| 2026-09-22 | GitHub PoC | Unvetted — public repository | abraxas/CVE-2026-87902 +21 more |
| 2026-10-01 | Exploit-DB | Direct — curated exploit code | WordPress 7.0.2 - Path Travesal |
Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.
Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.
| If the asset is | Remediate within | Table 1 row |
|---|---|---|
| Publicly exposed | 3 days + forensic triage → 2026-09-28 | 3 of 16 |
| Not publicly exposed | 14 days → 2026-10-09 | 11 of 16 |
BOD 26-04 replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.
CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →