Description
A high-severity security vulnerability in the WordPress core update process can expose websites to remote code execution during a short update window.
Tracked as CVE-2026-119977, the issue is associated with a Time-of-Check Time-of-Use (TOCTOU) race condition. During certain WordPress core updates, temporary files are extracted into the wp-content/upgrade directory. If those files are accessible through the web server, an attacker may attempt to reach the temporary WordPress installer before the update process removes it.
The vulnerability affects WordPress versions from 4.7 through 7.1.3, with fixes released for supported branches. WordPress 7.1.4 contains the security fix.
2. Technical Description
The vulnerability exists in the way vulnerable WordPress versions handle temporary files during core upgrades.
When a complete WordPress package is used, the updater extracts the new version into a temporary location under:
/wp-content/upgrade/On vulnerable installations, the temporary directory can have a predictable name. The extracted content can also include the WordPress installation files.
Because the directory is normally located within a web-served part of the WordPress installation, an attacker who correctly determines the temporary path can attempt to access the installer while the update is in progress.
The attack relies on timing. The attacker must reach the temporary installation during the short period between extraction and cleanup.
The vulnerability is classified as CWE-367 — Time-of-Check Time-of-Use Race Condition. The CVE record gives it a CVSS score of 8.1, with network attack vector, no required privileges, and no user interaction.
3. Attack Overview
The attack can be summarized as follows:
Vulnerable WordPress Website
↓
Administrator/System Starts Core Update
↓
WordPress Downloads Update Package
↓
Temporary Files Extracted
↓
Files Placed Under wp-content/upgrade/
↓
Temporary WordPress Installer Becomes Reachable
↓
Attacker Attempts to Identify Temporary Path
↓
Attacker Races the Update Process
↓
Temporary WordPress Environment Is Abused
↓
PHP Code Execution
↓
Potential Access to Live WordPress FilesThe attack window is short. However, security researchers observed automated probing shortly after the vulnerability was disclosed, indicating that attackers were actively looking for vulnerable installations.
4. Technical Analysis
The important security issue is not simply the existence of an upgrade directory. The problem is the combination of:
- A web-accessible temporary upgrade location
- Predictable temporary paths in vulnerable updater code
- Availability of WordPress installer files
- A short race window during the update
- Remote access without authentication
On affected versions, a complete-package update can place a usable WordPress copy inside the temporary directory.
An attacker who successfully reaches this temporary copy can potentially configure it against an attacker-controlled database and execute PHP code with the permissions of the web server.
This can provide access beyond the temporary directory because the web-server process may already have permissions to read or modify files belonging to the live WordPress installation.
The vulnerability is especially important because the first update that installs the security fix may still use the old vulnerable updater code. After the patched version is installed, subsequent updates use the improved behavior, including randomized temporary directory names.
5. Potential Impact
Successful exploitation could allow an unauthenticated attacker to execute PHP code with the privileges of the web server.
Potential consequences include:
- Unauthorized modification of WordPress files
- Reading sensitive files accessible to the web-server account
- Modification of website content
- Installation of malicious plugins or PHP code
- Creation or manipulation of WordPress administrator accounts
- Further compromise of the underlying web server
- Use of the compromised website for additional malicious activity
The actual impact depends on the permissions and security configuration of the affected WordPress environment.
6. Recommendations
Immediate Actions
1. Restrict access to the upgrade directory
Block direct web access to:
/wp-content/upgrade/For Nginx:
location ^~ /wp-content/upgrade/ {
deny all;
}For Apache:
Require all deniedIf .htaccess is the only available option:
RedirectMatch 403 ^/wp-content/upgrade/The restriction should be applied before the WordPress security update is performed.
2. Verify the restriction
Request:
/wp-content/upgrade/The expected response should be:
403 Forbidden3. Update WordPress
Upgrade affected installations to the appropriate fixed release.
For the current 7.1 branch:
7.1.3 → 7.1.4Other supported branches also received corresponding security fixes.
4. Investigate potentially compromised systems
Review:
- Web-server access logs
- WordPress administrator accounts
- Installed plugins
- Files under
wp-content/upgrade/ - Unexpected PHP activity
- Recent WordPress file modifications
Preventive Actions
Organizations should:
- Keep WordPress Core continuously updated.
- Restrict unnecessary web access to temporary and administrative directories.
- Monitor web-server logs for unusual PHP requests.
- Deploy a Web Application Firewall where appropriate.
- Monitor unexpected WordPress administrator account creation.
- Maintain offline or otherwise protected backups.
- Apply the principle of least privilege to web-server accounts.
- Monitor integrity changes to WordPress core files.
- Maintain an incident-response process for compromised WordPress sites.
- Avoid relying solely on automatic updates for high-risk vulnerabilities without understanding the update mechanism involved.
For older WordPress versions that no longer receive security updates, migration to a supported release is recommended. WordPress states that 4.6 and earlier no longer receive security updates.
8. Conclusion
CVE-2026-119977 demonstrates how an otherwise routine software-update process can become an attack surface.
The vulnerability allows an unauthenticated attacker to potentially reach a temporary WordPress installation during a narrow update window and execute PHP code on the affected server. The situation is particularly significant because exploitation has been observed and the initial update to the fixed release can still involve the vulnerable updater logic.
WordPress has released fixes across supported branches, including version 7.1.4. Organizations running affected installations should first restrict public access to the wp-content/upgrade directory, then apply the appropriate security update and investigate systems for signs of exploitation.
