Overview
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a high-severity vulnerability affecting WordPress Core to its Known Exploited Vulnerabilities (KEV) catalog, confirming that attackers are actively exploiting the flaw.
Tracked as CVE-2026-119977, the vulnerability has a CVSS score of 8.1 and involves a Time-of-Check Time-of-Use (TOCTOU) race condition. Successful exploitation could allow unauthenticated attackers to execute arbitrary code on affected servers during the WordPress Core upgrade process.
The vulnerability is associated with predictable, web-accessible staging paths used during full-package Core upgrades. Security patches were released in late October 2026, making it important for administrators to ensure their WordPress installations are updated.
Vulnerability Details
CVE ID: CVE-2026-119977
Affected Product: WordPress Core
Vulnerability Type: Time-of-Check Time-of-Use (TOCTOU) Race Condition
CVSS Score: 8.1
Severity: High
Authentication Required: No
Potential Impact: Arbitrary Code Execution
The vulnerability occurs because WordPress Core uses predictable and web-accessible staging paths during full-package upgrades.
A TOCTOU race condition occurs when a system checks a resource or its state and then uses that resource later, leaving a window in which an attacker may change or manipulate it.
In this case, the upgrade process creates a brief opportunity for an unauthenticated attacker to interfere with the staging process and potentially execute code on the affected server.
Exploitation requires an attacker to target the short upgrade window. Therefore, the vulnerability does not imply that every WordPress installation is continuously exposed to successful exploitation.
Exploitation Activity
CISA's addition of CVE-2026-119977 to the KEV catalog confirms that the vulnerability is being exploited in the wild.
Security research shared by Wordfence reported more than 18,500 requests targeting staged setup-config.php installer paths during the first 21 hours following public disclosure.
At the time of reporting, Wordfence had also blocked 12,632 attack attempts targeting the vulnerability within the previous 24 hours.
Additional telemetry from Previdian recorded three exploitation attempts against its honeypot sensors on October 30, 2026. These attempts originated from an IP address geolocated in the United Kingdom.
The reported activity demonstrates that attackers are actively scanning for vulnerable WordPress installations and attempting to exploit the upgrade process.
Security Impact
Successful exploitation of CVE-2026-119977 could allow unauthenticated attackers to execute arbitrary code on vulnerable WordPress servers.
Potential consequences include:
Unauthorized execution of code on the web server.
Compromise of the affected WordPress installation.
Unauthorized access to website data and server resources.
Potential installation of malicious scripts or additional payloads.
Further compromise of systems connected to the affected server.
The supplied reporting confirms active exploitation attempts but does not establish the extent of successful compromises or identify specific post-exploitation payloads.
Detection and Mitigation
WordPress administrators and hosting providers should prioritize remediation to reduce exposure to this vulnerability.
Recommended defensive actions include:
Apply security updates: Upgrade WordPress Core to a patched release addressing CVE-2026-119977.
Verify installed versions: Review WordPress installations across production, staging, and development environments.
Monitor upgrade activity: Investigate unexpected activity involving WordPress Core upgrade processes and staged
setup-config.phppaths.Review web server logs: Look for unusual requests targeting installer and upgrade-related paths, particularly during Core updates.
Restrict administrative access: Apply appropriate access restrictions to WordPress administration and server management interfaces.
Use security monitoring: Deploy web application firewalls (WAFs), endpoint monitoring, and intrusion detection capabilities to identify suspicious activity.
Review potentially affected systems: Investigate installations that were exposed during the upgrade window for signs of unauthorized code execution.
CISA has set November 6, 2026, as the remediation deadline for Federal Civilian Executive Branch (FCEB) agencies.
Conclusion
The active exploitation of CVE-2026-119977 highlights the security risks associated with race conditions in software update mechanisms. By targeting predictable staging paths during WordPress Core upgrades, attackers may be able to execute code without authentication.
With exploitation confirmed by CISA and security researchers reporting significant attack activity, WordPress administrators should prioritize installing the available patches, reviewing upgrade-related logs, and monitoring exposed installations for suspicious activity.
