# CVE-2026-119977 — WordPress

> As of 2026-10-31, CVE-2026-119977 is a HIGH-severity vulnerability in WordPress, CVSS v3.1 8.1, EPSS 0.6% (48.7th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-119977, most recently “Active Exploitation of WordPress Core Unauthenticated Upgrade-Window RCE (Versions 4.7 through 7.1.3) Hours After 7.1.4 Patch Release”.

**Last updated:** 2026-10-31

## What is CVE-2026-119977?

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.

The record classifies CVE-2026-119977 under weakness class [CWE-367](https://intel.threadlinqs.com/cwe/CWE-367). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 19 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.1 — HIGH (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.6% probability of exploitation in the next 30 days, higher than 48.7% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-31

## Is CVE-2026-119977 being exploited?

No public exploitation evidence for CVE-2026-119977 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-10-31. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

## Affected products and versions

- **WordPress Foundation**: WordPress

## How to fix CVE-2026-119977

No vendor patch reference has been recorded for CVE-2026-119977 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-119977

1 tracked threat in the Threadlinqs corpus references CVE-2026-119977, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Active Exploitation of WordPress Core Unauthenticated Upgrade-Window RCE (Versions 4.7 through 7.1.3) Hours After 7.1.4 Patch Release](https://intel.threadlinqs.com/threat/TL-2026-4804) — CRITICAL · 2026-10-30

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [wordfence.com](https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250?source=cve)
- [core.trac.wordpress.org](https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-wp-upgrader.php#L378)
- [core.trac.wordpress.org (class core upgrader)](https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/class-core-upgrader.php#L162)
- [core.trac.wordpress.org (update core)](https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/includes/update-core.php#L1549)
- [core.trac.wordpress.org (setup config)](https://core.trac.wordpress.org/browser/tags/7.1.3/src/wp-admin/setup-config.php#L282)

_Showing 5 of 8 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-119977
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
