CVE-2026-87902: An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the
Noroxi assessment
Priority: Now (action score 91/100)
- CISA has confirmed exploitation in the wild (Sep 25, 2026). Remediation deadline for US federal agencies: Sep 28, 2026.
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 95.7% (FIRST EPSS); higher than 99.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: WordPress WordPress 7.1.2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Patch today or shut off access. Upgrade to WordPress WordPress 7.1.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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.
- Published
- Sep 22, 2026
- Updated
- Sep 28, 2026
- EPSS
- 95.7% · 99th percentile
- CWE
- CWE-98
Report tools
Action score
91
Now
Patch today or shut off access.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 29 / 30 · 95.7%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Sep 25, 2026. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Sep 28, 2026.
Is WordPress on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wordpress | wordpress | cpe:2.3:a:wordpress:wordpress |
Using wordpress? Add it to your stack and be the first to know about CVEs like this one. (WordPress)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wordpress wordpressbefore 4.7.37
- wordpress wordpress4.8 and later · before 4.8.32
- wordpress wordpress4.9 and later · before 4.9.33
- wordpress wordpress5.0 and later · before 5.0.29
- wordpress wordpress5.1 and later · before 5.1.26
- wordpress wordpress5.2 and later · before 5.2.28
- wordpress wordpress5.3 and later · before 5.3.25
- wordpress wordpress5.4 and later · before 5.4.23
- wordpress wordpress5.5 and later · before 5.5.22
- wordpress wordpress5.6 and later · before 5.6.21
- wordpress wordpress5.7 and later · before 5.7.19
- wordpress wordpress5.8 and later · before 5.8.17
- wordpress wordpress5.9 and later · before 5.9.18
- wordpress wordpress6.0 and later · before 6.0.16
- wordpress wordpress6.1 and later · before 6.1.14
- wordpress wordpress6.2 and later · before 6.2.13
- wordpress wordpress6.3 and later · before 6.3.12
- wordpress wordpress6.4 and later · before 6.4.12
- wordpress wordpress6.5 and later · before 6.5.12
- wordpress wordpress6.6 and later · before 6.6.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
WordPress WordPress
- before 7.1.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | wordpress | from 0 | — |
| Debian:13 | wordpress | before 6.8.10+dfsg1-0+deb13u1 | 6.8.10+dfsg1-0+deb13u1 |
| Debian:14 | wordpress | before 7.1.2+dfsg1-1 | 7.1.2+dfsg1-1 |
Same product
wordpress: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-63030WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code ExecutionKEV72This week
- CVE-2026-60137WordPress < 7.0.2 - Facilitated SQL Injection via author__not_in in WP_QueryKEV60This week
- CVE-2019-8942WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an a60This week
Published before and after this one in the same product
- ← EarlierCVE-2025-58674Sep 23, 2025 · WordPress <= 6.8.2 - (Author+) Cross Site Scripting (XSS) Vulnerability23Monitor
- ← EarlierCVE-2026-64638Aug 7, 2026 · WordPress is vulnerable to a pre-auth reflected XSS vulnerability on the login screen.35Monitor
- ← EarlierCVE-2026-65640Aug 17, 2026 · WordPress is vulnerable to a remote code execution vulnerability via malicious Postscript file upload by an Author level user or higher.36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| WordPress WordPress | 7.1.2 | Vendor (CNA) |
| debian:wordpress | 6.8.10+dfsg1-0+deb13u1 · Debian:13 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Exploit-DB entry ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×25
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2026-10-01 |
| Nuclei detection template | Nuclei template CVE-2026-87902 | — |
| Proof-of-concept repository on GitHub | stars:35 | 2026-09-22 |
| Proof-of-concept repository on GitHub | stars:9 | 2026-09-22 |
| Proof-of-concept repository on GitHub | stars:44 | 2026-09-22 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-22 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-23 |
| Proof-of-concept repository on GitHub | stars:13 | 2026-09-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-23 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-09-23 |
| Proof-of-concept repository on GitHub | stars:3 | 2026-09-23 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-09-23 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-1 d
- Published
- CISA KEV+2 d
- TodayNov 1, 2026+40 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Robert (ressl)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1350 · Oct 16, 2026- WordPress Core Ayrıntılı Güvenlik Duyurusu (CVE-2026-87902)
Noroxi's write-up
Our blog post on this record: impact, how to check your site and the upgrade steps.
CVE-2026-87902: WordPress core flaw under attack. Are you affected?
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.