CVE-2026-119977 — WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution
WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Wordpress WordPress).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Wordpress | WordPress |
≥ 5.9.0 and ≤ 5.9.19≥ 7.1.0 and ≤ 7.1.3≥ 7.0.0 and ≤ 7.0.7≥ 6.9.0 and ≤ 6.9.10≥ 6.8.0 and ≤ 6.8.11≥ 6.7.0 and ≤ 6.7.10≥ 6.6.0 and ≤ 6.6.10≥ 6.5.0 and ≤ 6.5.13 and 17 more≥ 6.4.0 and ≤ 6.4.13≥ 6.3.0 and ≤ 6.3.13≥ 6.2.0 and ≤ 6.2.14≥ 6.1.0 and ≤ 6.1.15≥ 6.0.0 and ≤ 6.0.17≥ 4.7.0 and ≤ 4.7.38≥ 5.8.0 and ≤ 5.8.18≥ 5.7.0 and ≤ 5.7.20≥ 5.6.0 and ≤ 5.6.22≥ 5.5.0 and ≤ 5.5.23≥ 5.4.0 and ≤ 5.4.24≥ 5.3.0 and ≤ 5.3.26≥ 5.2.0 and ≤ 5.2.29≥ 5.1.0 and ≤ 5.1.27≥ 5.0.0 and ≤ 5.0.30≥ 4.9.0 and ≤ 4.9.34≥ 4.8.0 and ≤ 4.8.33 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.1 | CVSS 3.1 | High | 2.2 | 5.9 | security@wordfence.com via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | — | — | Wordfence via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: security@wordfence.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · wordpress foundation/wordpress
- Record published
- CVSS changed · 8.1
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 31, 2026 – Oct 31, 2026
- 1× Official description updated · Oct 31, 2026 – Oct 31, 2026
References
8 on the record
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/update-core.php
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php
- www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250
- wordpress.org/news/2026/10/wordpress-7-1-4/
- core.trac.wordpress.org/browser/tags/7.1.4/src/wp-admin/includes/class-wp-upgrader.php
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php
- core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-114570 WordPress Core <= 7.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Quick Edit 9d
- High CVE-2026-87902 WordPress Core Remote File Inclusion Vulnerability KEV Sep 22, 2026
- High CVE-2026-65640 Unrestricted Upload of File with Dangerous Type in WordPress Aug 17, 2026
- High CVE-2026-64638 Cross-site Scripting (XSS) in WordPress Aug 7, 2026
- Critical CVE-2026-63030 WordPress Core Interpretation Conflict Vulnerability KEV Jul 17, 2026
- Medium CVE-2026-60137 WordPress Core SQL Injection Vulnerability KEV Jul 17, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-119977 is "WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution", rated High. It affects WordPress (Wordpress); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.