What is CVE-2026-119977?
CVE-2026-119977 is a remote code execution (RCE) vulnerability in WordPress core that affects versions 4.7 through 7.1.3. It is a time-of-check time-of-use (TOCTOU) race condition (CWE-367): in a full-package core update, WordPress unpacks the new release into a predictable, web-accessible staging path under wp-content/upgrade/. An unauthenticated attacker can execute code on the server during that window, which lasts a few seconds. It was disclosed on October 28, 2026, the same day WordPress 7.1.4 shipped with the fix.
Wordfence, as CNA, assigned a CVSS 3.1 score of 8.1 (High). According to the finder, an attacker who exploits that window can make the updater overwrite the live wp-config.php with a malicious one, obtain an administrator account and, where administrators can install plugins, run PHP with the web server's privileges.
CISA added it to its Known Exploited Vulnerabilities (KEV) catalog on November 3, 2026. According to Beazley Security, exploitation attempts began within hours of the fix release. As of November 12, 2026, no source confirms a working public exploit.
Are you affected?
Short answer: if your sites have automatic updates enabled, they are most likely already on a fixed release. Still, confirm the version of every install, including staging or legacy ones. Also, according to the finder, the very update that installs the fix had one last exposed window: review your logs too.
A site is vulnerable if it runs WordPress 4.7 through 7.1.3 below its branch's fixed release and the web server serves wp-content/upgrade/, which is the default. The exposure comes back with every core update, including automatic ones. First fixed releases, published on October 28, 2026:
- 7.x:
7.1.4,7.0.8 - 6.x:
6.9.11,6.8.12,6.7.11,6.6.11,6.5.14,6.4.14,6.3.14,6.2.15,6.1.16,6.0.18 - 5.x:
5.9.20,5.8.19,5.7.21,5.6.23,5.5.24,5.4.25,5.3.27,5.2.30,5.1.28,5.0.31 - 4.x:
4.9.35,4.8.34,4.7.39
Always compare within your branch: for example, 6.8.11 is vulnerable and 6.8.12 is fixed. WordPress 4.6 and earlier no longer receive security updates: treat them as potentially vulnerable and unpatched.
Distribution packages, as of November 12, 2026:
-
Debian 13: fixed in
6.8.12+dfsg1-0+deb13u1(DSA-6596-1). Debian 12:6.1.9+dfsg1-0+deb12u1is still vulnerable with no fix published. -
Ubuntu: its security tracker has no entry for this CVE. If you use the
wordpresspackage, check its changelog. -
RHEL, AlmaLinux, Rocky Linux: WordPress is not in the RHEL or AlmaLinux base repositories. EPEL ships it and has published fixed builds (EPEL 9:
wordpress-6.9.11-1.el9). - cPanel, DirectAdmin, CloudLinux: we found no advisory from these providers. A site installed from wordpress.org, EPEL or a panel is affected unless it runs the fixed release.
How to check your server
Run WP-CLI as the site owner, not as root, and compare with the list above:
wp core version --path=YOUR_WP_PATH
wp core check-update --path=YOUR_WP_PATH
wp core check-update installs nothing. Do not run wp core update on a vulnerable site before blocking wp-content/upgrade/ (option B): according to the finder, it uses the same updater.
To find out whether the directory is blocked, request a non-existent PHP path inside it. If a CDN or WAF sits in front, run the test against the origin server:
curl -s -o /dev/null -w "%{http_code}\n" https://YOUR_DOMAIN/wp-content/upgrade/zz-deny-test/wp-admin/setup-config.php # expect 403; 404, 200 or 5xx = the rule is not working
Do not test only the directory URL: it can return 403 with no deny rule at all.
How to mitigate
| Option | Best for | Service interruption? | Durable? |
|---|---|---|---|
| A: update WordPress | Everyone, definitive fix | No | Yes |
B: deny web access to wp-content/upgrade/
|
Vulnerable sites, before updating | No (graceful reload) | As long as you keep the rule |
Option A: update WordPress
Back up the files and the database. If the site is still on a vulnerable release, apply option B first and confirm the 403, because the update that installs the fix still uses the old updater. Then update to your branch's fixed release (Dashboard > Updates or your usual method). If you use your distribution's package, install its security update; if there is none yet (for example on Debian 12), keep the option B rule in place.
Option B: deny web access to wp-content/upgrade/
WordPress never needs to serve that directory over HTTP; the finder and Patchstack recommend blocking it at the web server. Adjust the path if WordPress lives in a subdirectory or you use a custom WP_CONTENT_DIR; test on staging first. According to Patchstack, a security plugin is not enough, because the staged copy boots from its own files.
nginx: inside the site's server block. The ^~ modifier keeps nginx from evaluating the PHP location:
location ^~ /wp-content/upgrade/ {
deny all;
}
Test the configuration and reload nginx. The reload does not drop open connections:
nginx -t && systemctl reload nginx
Apache 2.4: in the virtual host, with the site's real path:
<Directory "/var/www/html/wp-content/upgrade">
Require all denied
</Directory>
Test and reload Apache; this reload does not drop connections either:
apache2ctl configtest && systemctl reload apache2 # Debian/Ubuntu
apachectl configtest && systemctl reload httpd # RHEL family
.htaccess only (shared hosting): add this line to the .htaccess in the WordPress root, above the rewrite block. It requires AllowOverride FileInfo; without it, Apache returns a 500 error for the whole site, so test it first. Never create an .htaccess inside wp-content/upgrade/: the unpatched updater deletes everything there.
RedirectMatch 403 ^/wp-content/upgrade/
On cPanel/WHM or DirectAdmin, do not edit the panel-generated Apache or nginx configuration, because it is regenerated: use the panel's own includes or custom templates and repeat the curl test after every rebuild.
Detecting signs of compromise
Beazley Security recommends searching web server and WAF logs for requests to PHP files under wp-content/upgrade/, especially copies of setup-config.php. The paths are the Debian/Ubuntu defaults; adjust them on other systems.
zgrep -hE "wp-content/upgrade/.*\.php" /var/log/apache2/access.log* /var/log/nginx/access.log*
zgrep -H "setup-config.php" /var/log/apache2/access.log* /var/log/nginx/access.log*
The most suspicious hits are requests close to a core update or across many staging directories; a 403 or 404 means they were blocked. No hits proves nothing if logs rotate quickly or a CDN hides requests.
Review the staging directory (not while an update is running; preserve evidence before deleting anything):
ls -la YOUR_WP_PATH/wp-content/upgrade/
find YOUR_WP_PATH/wp-content/upgrade/ -name "*.php" -ls
On 7.1.4 or later, it should hold nothing but an index.php between updates; before the fix it is normally empty or missing. Any other content deserves a closer look. A clean result does not rule out an earlier attack, because the directory is emptied on every update.
Also look for administrator accounts you do not recognize, unexpected plugins, PHP files you did not place and changes to wp-config.php. As of Beazley's advisory, no IP addresses or hashes had been published. Compare core files against the official checksums:
wp core verify-checksums --include-root --path=YOUR_WP_PATH
Success does not prove the site is clean: checksums do not cover wp-config.php or wp-content, which is exactly what this attack changes.
After mitigating
- On every install, even with automatic updates, confirm that core is intact and on its branch's fixed release:
wp core verify-checksums --path=YOUR_WP_PATH && wp core version --path=YOUR_WP_PATH - Review your logs around the time the fix was installed: updating does not show that the site escaped an earlier compromise.
- If you keep the option B rule, test it again with
curlafter every web server configuration change. - If you suspect a compromise, preserve all logs before cleaning up. Then rotate the credentials and secrets WordPress can access, including the database credentials.
Need help?
Open a ticket at soporte.telecu.cloud and reference: CVE-2026-119977.
Sources
- WordPress.org: WordPress 7.1.4 announcement
- WordPress.org HelpHub: version 7.1.4 and fixed releases per branch
- CVE Program: CVE-2026-119977 record
- CISA: Known Exploited Vulnerabilities catalog
- Debian Security Tracker: CVE-2026-119977
- Picus Security: the finder's write-up
- Patchstack: analysis of the 7.1.4 security release
- Beazley Security Labs: BSL-A1241 advisory on active exploitation