WordPress Core: attackers can run their own code
OFFICIAL NAME: WordPress Core Remote File Inclusion Vulnerability
WHAT IT IS · WEBSITE OR ONLINE STOREIt runs public websites, online stores or the software behind them.
DO THIS FIRSTAsk whoever runs your website or store to update it. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY 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.
WHY THIS VERDICT Attacks are confirmed. The vulnerability is 49 days old, so many systems are likely still unpatched. Ready-made attack tools are public. The exploit prediction score is 96%.
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. Ready-made attack tools are public.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- READY TO USE
How far has it climbed?
01 TALK
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCECVE-2026-87902 discussed publicly (CIRCL sighting). CVE-2026-87902 discussed publicly (CIRCL sighting).
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESWordPress 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. CISA Vulnrichment marks CVE-2026-87902 as actively exploited.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLIC
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Sep 28, 2026, has passed. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run WordPress Core? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- Attack activity. SEP 22, 2026CISA Vulnrichment marks CVE-2026-87902 as actively exploited
- SEP 22, 202625 public GitHub repositories claim a proof of concept for CVE-2026-87902
- SEP 23, 2026Vulnerability CVE-2026-87902 confirmed by a researcher (CIRCL sighting)
- Attack activity. SEP 24, 2026WordPress Core Remote File Inclusion Vulnerability
- SEP 30, 2026Exploit-DB entry: WordPress 7.0.2 - Path Travesal
- OCT 24, 2026CVE-2026-87902 discussed publicly (CIRCL sighting) (6 reports, latest NOV 10)
SOURCES
- [1] nuclei-templates: Nuclei scan template: WordPress Core - PHP Template Path Traversal, OCT 24
- [2] CIRCL Vulnerability-Lookup sightings: CVE-2026-87902 discussed publicly (CIRCL sighting), NOV 10
- [3] Exploit-DB: Exploit-DB entry: WordPress 7.0.2 - Path Travesal, SEP 30
- [4] CISA Known Exploited Vulnerabilities: WordPress Core Remote File Inclusion Vulnerability, SEP 24
- [5] CIRCL Vulnerability-Lookup sightings: Vulnerability CVE-2026-87902 confirmed by a researcher (CIRCL sighting), SEP 23
- [6] PoC-in-GitHub: 25 public GitHub repositories claim a proof of concept for CVE-2026-87902, SEP 22
- [7] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-87902 as actively exploited, SEP 22
- [8] CIRCL Vulnerability-Lookup sightings: 5 more reports