Evidence used
- CISA confirms exploitation in the wild.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 45.50% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-87902High confidence
WordPress Core Remote File Inclusion Vulnerability
WordPress · Core
Official source article: GitHub GHSA-7HP8-65CH-5WHP ↗. Check the applicable product and release in the original source.
8.1HighCVSS 3.1
Protect now
Fix not verifiedCISA confirms exploitation in the wild and lists 2026-09-28 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 25 Sep 2026
Compensating controls
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs WordPress Core and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | wordpress | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.8.10+dfsg1-0+deb13u1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | wordpress | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | wordpress | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.1.2+dfsg1-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | wordpress | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.1.2+dfsg1-1 | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | wordpress | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 2 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-87902 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitywordpress: WordPress: Remote code execution via page template resolution vulnerability
The vendor explicitly states that these products are not affected by this CVE.
- All currently supported Red Hat products
- Summary
- A flaw was found in WordPress. An unauthenticated attacker can exploit a vulnerability in the `get_page_template()` function's page-template resolution. This allows the attacker to include a chosen readable local PHP file from outside the active theme directories. If specific server and active theme pre-conditions are met, this can lead to remote code execution (RCE), enabling the attacker to run arbitrary code on the affected system.
- Remediation
- No remediation text is recorded.
CISA confirms exploitation in the wild and lists 2026-09-28 as the remediation due date.
Fix not verified01
What, why and how
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.
What
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
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in require, include, or similar functions.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
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
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in require, include, or similar functions.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-09-25.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-98 ↗
CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion'). The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in require, include, or similar functions.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- WordPress: < 7.1.2
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Unauthenticated path traversal in page-template resolution leading to conditional RCE · Advisory · WordPress/wordpress-develop · GitHub →Original publisher ↗Searchable text snapshot · Captured 28 Sep 2026WordPress / wordpress-develop Public Notifications You must be signed in to change notification settings Fork 3.7k Star 3.5k Code Pull requests 3.5k Actions Security and quality 43 Insights Additional navigation options Code Pull requests Actions Security and quality Insights Unauthenticated path traversa
04
Evidence and provenance
Published 22 Sept 2026 · Last source change 26 Sept 2026, 03:55 UTC · CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-09-23
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-84555
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-952.support@hackerone.com ↗
- Before
- remediation: cyber.gc.ca/wordpress-security-advisory-av26-952 · vendor advisory: github.com/GHSA-7hp8-65ch-5whp
- After
- vendor advisory: github.com/GHSA-7hp8-65ch-5whp
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.support@hackerone.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: github.com/GHSA-7hp8-65ch-5whp.support@hackerone.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: github.com/GHSA-7hp8-65ch-5whp
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-952.CISA KEV ↗
- Before
- remediation: cyber.gc.ca/wordpress-security-advisory-av26-952
- After
- no authoritative guidance recorded
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.CISA KEV ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Canadian Centre for Cyber Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.ENISA EUVD ↗
- Before
- not listed in ENISA EUVD known-exploited dataset
- After
- listed in ENISA EUVD known-exploited dataset (EUVD-2026-84555)
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-952.CISA KEV ↗
- Before
- remediation: cyber.gc.ca/wordpress-security-advisory-av26-952
- After
- no authoritative guidance recorded
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.CISA KEV ↗
- Before
- Mitigation available
- After
- Awaiting fix
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Canadian Centre for Cyber Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- ENISA EUVD mappingEUVD-2026-84555 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-84555"}
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-952.CISA KEV ↗
- Before
- remediation: cyber.gc.ca/wordpress-security-advisory-av26-952
- After
- no authoritative guidance recorded
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.CISA KEV ↗
- Before
- Mitigation available
- After
- Awaiting fix
- CISA KEV stateCISA KEV now confirms exploitation in the wild.CISA KEV ↗
- Before
- not listed in CISA KEV
- After
- listed in CISA KEV since 2026-09-25
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.