> ## Documentation Index
> Fetch the complete documentation index at: https://blog.onetsolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# WordPress CVE-2026-119977: RCE during core updates, fix it now

> WordPress CVE-2026-119977 is actively exploited: remote code execution during core updates, 4.7 to 7.1.3. Fixed version per branch and how to check your site.

*Published on November 16, 2026*

> [!WARNING]
>
> **CVE-2026-119977 — WordPress core, versions 4.7 to 7.1.3.** During a full core update, an unauthenticated attacker can run code on the server. CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 3, 2026. WordPress 7.1.4 fixes it, and the fix was backported to every branch down to 4.7. Check the version of each site today.

## The bug in two sentences

When WordPress updates its core from the full package, it extracts the new files to a predictably named directory inside the `upgrade` folder served by the web server. An attacker who wins the race against that extraction can execute code remotely, with no account on the site.

It is a time-of-check time-of-use race condition (CWE-367): the attack window is the length of the update.

Wordfence, which assigned the CVE, scores it **8.1** under CVSS 3.1 (`AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`); NVD carries the same score. Attack complexity is high: the attacker has to hit the update window. Red Hat rates it "Important". The WordPress project, in its advisory GHSA-4w3m-c66w-69mg, rates it "Low".

Umut Bayram (Picus Security) found the flaw. WordPress 7.1.4 shipped on October 28, 2026.

> [!NOTE]
>
> A KEV entry means exploitation has been seen on real systems. That, more than the gap between scores, should set your priority.

## Sizing your exposure

The question to ask: **does every one of your sites run the fixed version of its branch?**

| Profile | Exposure | Action |
| - | - | - |
| WordPress 4.7 to 7.1.3 installed by hand, with WP-CLI or with Softaculous, on a VPS or web hosting | **High**: actively exploited | Update to the fixed version of the branch |
| Debian 13 (trixie) `wordpress` package older than `6.8.12+dfsg1-0+deb13u1` | **High** | `apt` from the security repository |
| Debian 12 (bookworm) `wordpress` package | **High** | Watch the Debian tracker and apply the update as soon as it ships |
| EPEL `wordpress` package on RHEL or AlmaLinux | Depends on the installed version | `dnf upgrade wordpress` |
| WordPress at the fixed version of its branch, or 7.1.4 and later | Not affected | None |
| WordPress older than 4.7 | Outside the declared range, but the branch no longer gets fixes | Move to a maintained branch |

Fixed versions, per the WordPress project's advisory:

| Branch | Fixed version | Branch | Fixed version |
| - | - | - | - |
| 7.1 | `7.1.4` | 5.8 | `5.8.19` |
| 7.0 | `7.0.8` | 5.7 | `5.7.21` |
| 6.9 | `6.9.11` | 5.6 | `5.6.23` |
| 6.8 | `6.8.12` | 5.5 | `5.5.24` |
| 6.7 | `6.7.11` | 5.4 | `5.4.25` |
| 6.6 | `6.6.11` | 5.3 | `5.3.27` |
| 6.5 | `6.5.14` | 5.2 | `5.2.30` |
| 6.4 | `6.4.14` | 5.1 | `5.1.28` |
| 6.3 | `6.3.14` | 5.0 | `5.0.31` |
| 6.2 | `6.2.15` | 4.9 | `4.9.35` |
| 6.1 | `6.1.16` | 4.8 | `4.8.34` |
| 6.0 | `6.0.18` | 4.7 | `4.7.39` |
| 5.9 | `5.9.20` | | |

To find a site's version:

```bash theme={null}
# From the site root, with WP-CLI
wp core version

# Without WP-CLI, the version lives in this file
grep "wp_version =" wp-includes/version.php
```

## Updating WordPress per install type

The WordPress project's advisory lists no workaround: the core update is the fix.

### WordPress installed by hand or with WP-CLI

Sites that support automatic background updates receive the fix on their own. Check the version anyway: a site with automatic updates turned off, or with read-only core files, stays where it is.

```bash theme={null}
# Back up the database before updating
wp db export before-update.sql

# Stay on the current branch and take its latest fixed release
wp core update --minor

# Or go straight to the latest release, 7.1.4 or later
wp core update

# Database schema migration, required after a core update
wp core update-db

# Check
wp core version
```

From the admin area, the update is under **Dashboard → Updates → Update Now**.

### cPanel web hosting

On OnetSolutions web hosting, [Softaculous](https://help.onetsolutions.net/web-hosting/softaculous) shows an update button for every installed application that has one. It is the fastest way to check several sites at once.

### Debian and derivatives (`wordpress` package)

| Release | Fixed `wordpress` package |
| - | - |
| Debian 13 (trixie), security repository | `6.8.12+dfsg1-0+deb13u1` |
| Debian testing (forky) and unstable (sid) | `7.1.4+dfsg1-1` |
| Debian 12 (bookworm) | not yet listed by the Debian tracker |

```bash theme={null}
# Debian: update the wordpress package
sudo apt update && sudo apt install --only-upgrade wordpress
```

### RHEL and AlmaLinux (EPEL `wordpress` package)

WordPress is not shipped in RHEL's repositories. The `wordpress` package comes from EPEL, which carries `6.9.11` (EPEL 9 and EPEL 10.2) and `7.1.4` (EPEL 10.3 and 10.4), all fixed.

```bash theme={null}
# RHEL, AlmaLinux: update the EPEL wordpress package
sudo dnf upgrade wordpress
```

## Checking the fix

```bash theme={null}
# Core version, to compare with the branch table
wp core version

# Core files identical to those published by WordPress.org
wp core verify-checksums

# For a package install: installed version
apt policy wordpress   # Debian
rpm -q wordpress       # RHEL, AlmaLinux (EPEL)
```

`wp core verify-checksums` reports any modified or added core file. Since the flaw is being exploited, review the administrator accounts too:

```bash theme={null}
# Administrator accounts and creation date
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
```

An unknown account or a modified core file: treat the site as compromised, restore an earlier backup, update, then rotate every password.

## What next?

Automatic minor updates carry the core's security fixes: keep them on, as our [WordPress hardening checklist](https://blog.onetsolutions.net/en/secure-wordpress-after-wp2shell.md) explains. On a VPS, also turn on [automatic security updates](https://blog.onetsolutions.net/en/automatic-security-updates-linux-vps.md) for system packages. For another recent flaw, read [the APT vulnerability CVE-2026-109518](https://blog.onetsolutions.net/en/apt-cve-2026-109518.md). For any technical question, open a ticket from your [OnetSolutions customer area](https://help.onetsolutions.net/console/support).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.