
Editorial illustration; it does not depict a real incident or dashboard.
If your WordPress site is still running an affected release, the practical question is simple: has it received the fix for CVE-2026-87902, and can you verify that the update completed? WordPress published the security fix on September 22, 2026. CISA later added the vulnerability to its Known Exploited Vulnerabilities catalog, while FIRST’s EPSS data for November 18 gives it a high exploitation-likelihood signal. That makes version verification and patching the priority; it does not tell us that any particular site has been compromised.
The vendor advisory says an unauthenticated attacker could make page-template resolution include a readable local PHP file outside the active theme directories. Remote code execution depends on additional theme and server conditions. Here is how to check your exposure without confusing a vulnerability record, a severity score and evidence about your own site.
Summary
- WordPress lists affected releases from 4.7.0 through specific branch patches; the fix first appeared in 7.1.2 and was backported to maintained security branches.
- Check the version actually installed on every site, then update to the latest available release for its branch; WordPress 7.1.5 is the latest release as of November 21, 2026.
- CVSS describes technical severity; CISA KEV confirms known exploitation, and EPSS estimates exploitation likelihood across the population. None confirms compromise of your site.
- If the site was exposed while unpatched, patch first and review logs, files, users and host security records for signs of unauthorized access.
What CVE-2026-87902 means for a WordPress site
A CVE identifier follows the pattern CVE-YYYY-NNNNN (the final number can now be longer than five digits). The CVE Program, coordinated by MITRE and its numbering authorities, assigns a stable public name to a specific reported vulnerability. For example, CVE-2021-44228 identifies Log4Shell in Apache Log4j. The identifier is not itself a risk rating or remediation instruction. WordPress published security release 7.1.2 on September 22, 2026, and linked this issue to CVE-2026-87902 and GHSA-7hp8-65ch-5whp.
The GitHub advisory lists affected WordPress core versions as 7.1.0–7.1.1, 7.0.0–7.0.5, 6.9.0–6.9.8, and corresponding earlier ranges down to 4.7.0–4.7.36. Patched releases include 7.1.2, 7.0.6, 6.9.9, 6.8.10 and the branch-specific fixes listed in the advisory through 4.7.37. The fix was backported to all branches then eligible for security updates; that does not mean every old branch remains supported today. Prefer the latest supported WordPress release that your site can run, not merely the first patch version.
The flaw is in page-template resolution. The advisory describes two relevant preconditions for the documented route: the active parent or child theme has a top-level directory beginning with page-, and a chosen readable local PHP file exists on the server. If those conditions and other environment details align, inclusion can lead to remote code execution. This is why “unauthenticated” is important but not the whole risk assessment: the attacker does not need a WordPress account, while successful impact still depends on deployment conditions.
CVSS, KEV and EPSS answer different questions
The WordPress/GitHub advisory rates this issue Critical and lists a CVSS v4 base score of 9.2, with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. The advisory identifies CWE-98, improper control of a filename used in a PHP include/require statement. Some external reporting presents a CVSS v3.1 score instead; score versions use different metrics, so do not compare those values as though they were one measurement.
CVSS scores run from 0.0 to 10.0 and summarize technical severity. CVSS v3.1 separates Base, Temporal and Environmental metric groups: the Base group describes intrinsic characteristics, Temporal adjusts for factors such as exploit maturity and remediation availability, and Environmental reflects the organization’s deployment context. The vendor’s published score here is v4.0 Base, not a customized score for your hosting setup. A high score should prompt attention, but does not alone establish the immediate business risk for each installation.
CISA’s KEV catalog marks CVE-2026-87902 as known exploited and records a September 25, 2026 addition date. The NVD detail page also displays that KEV status. CISA’s public catalog endpoint returned an access error during this check, so the status was cross-checked against the readable NVD page and official WordPress advisory references rather than treated as a direct live catalog query.
FIRST’s EPSS API returned a score of 0.95769 and percentile 0.99873 dated November 18, 2026. EPSS estimates the likelihood that exploitation activity will be observed for a CVE in the next 30 days; it is not a probability that your specific site will be attacked or compromised. Its high value, alongside KEV status, reinforces that teams should not defer checking exposure. Your site’s installed version, internet reachability, theme and server conditions still matter.
The CVE record, NVD enrichment, vendor advisory, KEV and EPSS are separate sources with different purposes. CVE identifies the flaw; NVD adds structured vulnerability information; the vendor explains affected WordPress releases and fixes; KEV flags known exploitation; EPSS supplies a changing forecast signal. A vulnerability moves from discovery and responsible disclosure through assignment and vendor patch preparation to release and public disclosure. The CVE identifier helps connect these records, but publication does not install the patch. Do not treat one source as a substitute for the others.
A calm site-owner response
1. Find the installed core version
Check Dashboard → Updates and confirm the version shown after any update. If you manage multiple sites, hosting control panels, Composer deployments or managed WordPress services, check each instance and confirm which site and environment it represents. A deployment manifest or WP-CLI can help teams inventory installations, but verify the value against the running site.
At the time of writing, WordPress 7.1.5 is the latest release. The relevant security fix was first included in 7.1.2, with fixes backported to older branches. Update to the latest supported branch release available for your site. If an old installation cannot move to a current branch, confirm the exact backported security version and plan a supported upgrade; do not assume an unsupported version received every later fix.
2. Back up and update through your normal process
Take a restorable backup or use your managed host’s tested update process. Apply the current core update from the WordPress dashboard, WP-CLI or your deployment pipeline. If you use Composer, update the locked dependency through that workflow rather than editing vendor files by hand. Do not pin the site to 7.1.2 just because it contains this fix: later security and maintenance releases may add other corrections.
Test sign-in, the front page, page templates, forms, publishing and key integrations after the update. Keep a rollback route available, but avoid rolling back to a vulnerable release as a long-term fix. If the update fails, ask your host or developer to resolve that deployment issue promptly.
3. Assess whether the vulnerable state was exposed
If logs are available, preserve them and review the period when the site was both affected and reachable from the internet. Look for unusual requests related to page-template resolution, unexpected PHP files, new administrator accounts, modified core or theme files, and unfamiliar plugins. The official advisory describes the vulnerable behavior but does not provide a universal log signature that proves an exploit attempt. A suspicious request is an indicator to investigate, not proof of successful compromise.
If you find evidence of unauthorized changes, updating alone is not incident response. Contact your hosting provider or security responder, isolate the affected site if needed, preserve evidence, rotate credentials from a clean device and restore only from a known-good backup after identifying how access occurred. A web application firewall rule may be a useful temporary compensating control only if it is verified for this attack path; it is not a replacement for installing the vendor fix.
4. Confirm the result and keep watching
After the update, confirm the running version and check that the site’s files match the expected release. Use WordPress’s built-in update screen or your deployment system’s inventory; a cached admin page or a successful job message is not enough. Continue monitoring authentication, file integrity and server logs according to your normal process.
What CVE, CWE and CPE mean here
CVE is the identifier for this specific vulnerability. CWE-98 is a weakness category describing the underlying unsafe file-include control. CPE is a structured naming scheme that vulnerability tools may use to match products and versions; because vendor release ranges can be more precise than broad product names, verify a scanner match against WordPress’s advisory before acting. A scanner’s “WordPress affected” label is a lead for investigation, not an inventory record.
The lifecycle is also more than a CVE number: a researcher responsibly disclosed the issue, WordPress assessed it and prepared a fix, the vendor released patched versions and public details, and databases and exploitation feeds added their own records. Vulnerability tools such as Dependabot, Snyk and Trivy can help teams find affected code or dependencies; an NVD API integration can enrich inventory records. For a hosted WordPress site, also check the WordPress release/advisory and your host’s actual installed-version inventory. A software-component scanner may not know which WordPress instance serves production traffic, and a version match still needs verification against the vendor’s affected ranges. Publication gives site owners information to act; it does not itself install the patch.
Mistakes to avoid
- Checking only the main website. Staging, campaign and forgotten WordPress installs may be internet-reachable too.
- Stopping at “the update ran.” Verify the version that is actually serving traffic.
- Assuming the CVSS score proves compromise. It measures severity, not local incident status.
- Relying on a WAF or hiding version strings. Neither repairs vulnerable core code.
- Treating a clean scan as proof. Scanners can miss installations or environment-specific indicators.
Our WordPress security update checklist covers a general post-update review, while the guide to testing a WordPress backup restore explains how to rehearse recovery before you need it.
Why this matters
The combination of a vendor patch, CISA KEV status and a high EPSS signal makes this worth acting on even though the disclosure is not brand new. A site owner does not need to reverse-engineer the exploit: confirm whether a vulnerable version is running, apply the current fix, and investigate separately if the site may have been exposed or altered.
My Take
The most useful first check is the version inventory. It turns a broad security headline into a specific question for each site and avoids spending time debating severity while an affected installation remains unpatched.
Bottom Line
Check every WordPress installation, update to the latest supported release for its branch, verify the running version and review evidence of exposure if it was vulnerable and public. KEV and EPSS raise the priority; they do not tell you whether your individual site was breached.